Page 1 of 1
locations of code and builds for 1.7
Posted: 17.07.2017, 16:29
by John Van Vliet
feel free to add or rearrange things
my Linux 64 edits of the last svn code are on my git page
this WILL be a SPICE ( 65 ,will be 66 soon) version seeing as it is a upload of MY code i use
Posted: 24.07.2017, 09:07
by K.A.V
John Van Vliet, Do you have a Linux + SPICE version of the working class with the latest GitHub code?
And why do not you work mostly in the Celestia repository? You can join forces
Posted: 25.07.2017, 01:38
by John Van Vliet
i started this branch a long time ago
-- just recently put it on github
Posted: 28.07.2017, 15:56
by K.A.V
John Van Vliet, Your Celestia (Spice) can be compiled for Windows?
Posted: 13.02.2018, 19:44
by codrinb
It would be nice to rebase to
https://github.com/CelestiaProject/Celestia, to avoid too much forking and effort duplication
Posted: 14.02.2018, 07:26
by John Van Vliet
the issue is the main base is becoming Microsoft mostly
with just new things added on top of a aging code base that is in NEED of a clean up and compile warning fixes
along with updating to the current c++ standard
currently c++11 and gcc 4.8
Posted: 14.02.2018, 20:20
by Janus
Not sure it applies or not, but my current code that compiles in x86 & x64 via VS2013/15, also compiles with the mingw 5.30 that comes with QT creator.
Of course I can't link it to test yet because I have not figured out how to make libs with mingw.
However, as I understand it Mingw is basically gcc with a twist.
So what works on mingw, should work on gcc.
On my fork I have been working on switching to size_t for as many return parameters in particular as I can.
From what I can see, speaking as a non C/C++ programmer who is just looking at patterns.
Is that to much of the code is dependent on 32 bit return sizes.
Other sections assume that char will be eight bit, or that string are plaintext in english.
Which is why I have been trying out size_t for return values.
Major restructuring is beyond my skill or knowledge.
I still can't even do opengl, the guides do me no good because they use matrix math, which is a complete mystery to me.
You would think that somewhere on the internet someone did it different.
I will make a Linux VM and test if my code will compile via QT for linux.
Janus.
Posted: 15.02.2018, 04:54
by John Van Vliet
I have not figured out how to make libs with mingw.
you use "dlltool" to link the *.la's and and something else i can not remember it's file extension , to make a dll
Is that to much of the code is dependent on 32 bit return sizes.
yes and this needs to be moved into 64 bit , but that is not a needed NOW thing
Posted: 15.02.2018, 07:33
by Janus
I am actually not wanting to make DLL files, I want to use straight lib files, or however mingw labels them.
As I have done from the beginning, I try to avoid external libraries as much as I can.
Not looking forward to fighting the linux version of DLL h3ll with QT, it is a mess.
Working in a VM using Devuan W/Mate desktop, the most win95 like I one can find.
I will post when I am able to get my code to compile and run.
Janus.
Posted: 16.02.2018, 14:21
by codrinb
What is the relationship among these repos:
https://github.com/JohnVV/MyCelestiaBuild- Celestia 1.7.x?? with focus on Linux??
https://github.com/CelestiaProject/Celestia- Celestia 1.7.x?? with focus on Windows??
- it already has 29 forks
https://github.com/CelestiaProject/Celestia/network https://github.com/erickt/celestia- Celestia 1.6.x?? with focus on Mac??
I am quite confused.
Which one is the latest code? Can it all be merged together in one place and then use fork/branch/tag so it is easier to develop and collaborate?
-Codrin
Added after 4 minutes 14 seconds:@John,
Just noticed your answer above.
As I feared.
Which branch at least has the latest .cpp code?
It thought the latest code is at the
https://github.com/CelestiaProject/Celestia, so I started (on my fork) to bring it up to date to compile on Mac. It's quite a delta between Windows and Mac.
I noticed that someone did some work on this
https://github.com/erickt/celestia to make it work on a Mac, however, looks like older (1.6.x code).
I just hope all of them could come together nicely in on single place
-Codrin
Posted: 17.02.2018, 16:31
by selden
Codrin,
I think it's overoptimistic to hope that any one repo has "the latest code." Each is a branch off the preliminary v1.7 code on SourceForge, started by someone frustrated with the lack of official ongoing development. Each will have new code that the others don't.
Posted: 17.02.2018, 16:49
by John Van Vliet
fractured code is one of the first signs ...
.
Posted: 17.02.2018, 17:07
by Janus
@Codrin
For instance.
In mine, I have planets, moons, and some other stuff that displays it's RaDec & Dist in real time when it is selected, which to my knowledge no one else does.
To help amateur astronomers find stuff using a familiar interface.
I have also implemented alphabetized loading of addons, so load order is no longer dependent on the mood your Computer/OS/Filesystem is in.
I moved the observer distance information to the lower right because it makes more sense to me there.
And those are just the differences that show on the outside.
There are more under the hood so to speak.
ALexell is the one who managed to acquire the old forum, I had been trying and failing.
He is hosting the site, and running the forum.
He should be providing guidance and direction while integrating the best or most agreed upon ideas.
Instead, there is little to no movement or contact.
The forum disappears, then returns, and sometimes loses posts when it does.
I really began working on my fork when Alexell decided to go pure QT for everything, a move I wholeheartedly disagree with.
I disagree because I have fought instances where having multiple versions on the same system conflict with each other.
I do nothing for the Mac version because I do not own one, nor shall I ever.
I am still learning Linux, and I am horrible at it because I can not find any pattern to where things are scattered.
Yet John Van Vliet uses it everyday, and has a fork dedicated to Linux.
I for one had hoped that having the forum back up would provide a focus and a center, which sadly, it has not.
Unilateral decisions such as QT only and forever, serve to divide more than unify.
As for me, if I can ever figure out Git, I will be putting my code up on my site, and just monitoring here.
That includes all of the support libraries as well, Lua, Jpeg, Png, etc.
I have all of them setup to provide the static libraries to be linked in.
As I can, I am adding more compiler support so they can be kept up to date as their core projects progress as well.
Vs2013 now, W/VS2015 soon.Mingw when I can figure it out.
I am currently working on QT in Devuan Linux via QT.
There are a lot of skilled people here, many of whom are better than I am at this stuff, I am a complete amateur on the C/C++ front.
Those skills need to be brought together, coordinated to bring their strengths to the fore, and cover for each other's weaknesses.
One of the reasons Celestia.Sci makes consist progress, even if it is slow, is that they communicate.
The lack of that here worries me.
Hence me going my own way, doing my own thing.
If you don't like the dance, tell whomever to fork off, you are going to do your own thing.
My code is there to be used if anyone wants, which is the beauty and grace of open source.
I will be posting an updated code, and some binaries, as soon as I get done cleaning up the mess I made fixing the loading order, and some other stuff.
So don't lose hope.
Even if this place implodes, Celestia lives on, and will coalesce somewhere else in its own time.
Janus.