64 bit Celestia in addition to 32 bit?

The place to discuss creating, porting and modifying Celestia's source code.
Topic author
podboq
Posts: 1
Joined: 24.07.2019
With us: 4 months 13 days

64 bit Celestia in addition to 32 bit?

Post #1by podboq » 24.07.2019, 04:01

Will Celestia be updated to 64 bit so that it continues to work with the latest macOS release? macOS is dropping support for 32 bit applications in the upcoming OS... I'd hate to lose it.

onetwothree
Developer
Posts: 340
Joined: 22.09.2018
With us: 1 year 2 months

Post #2by onetwothree » 24.07.2019, 08:48

Just follow INSTALL file instructions and build it yourself.

Hoeveer
Posts: 1
Joined: 11.08.2019
With us: 3 months 26 days

Post #3by Hoeveer » 11.08.2019, 06:38

Obvious troll is obvious.

From the INSTALL document:

Code: Select all

Celestia Install instructions for OS X
--------------------------------------

Currently not supported as nobody in the Team has access to an OS X system.


Thanks for nothin'

onetwothree
Developer
Posts: 340
Joined: 22.09.2018
With us: 1 year 2 months

Post #4by onetwothree » 11.08.2019, 17:55

Hoeveer wrote:Thanks for nothin'

Please check .travis.yml files, it contains enough info to build.

ekke85
Posts: 1
Joined: 15.11.2019
With us: 21 days 6 hours

Post #5by ekke85 » 15.11.2019, 17:27

I had the same problem, you need to compile and install the program from source.
Follow the instructions "Celestia Install instructions for macOS, qt-only" on their github INSTALL file https://github.com/CelestiaProject/Celestia/blob/master/INSTALL

Once it is installed you should be able to launch the program from /usr/local/bin/celestia-qt

Markerz
Posts: 76
Joined: 29.01.2009
Age: 24
With us: 10 years 10 months
Location: Hangzhou, China

Post #6by Markerz » 16.11.2019, 03:22

ekke85 wrote:I had the same problem, you need to compile and install the program from source.
Follow the instructions "Celestia Install instructions for macOS, qt-only" on their github INSTALL file https://github.com/CelestiaProject/Celestia/blob/master/INSTALL

Once it is installed you should be able to launch the program from /usr/local/bin/celestia-qt

In addition to that, you can find 1.6.2 beta on the release section of GitHub too which has the same UI as the previous version, https://github.com/CelestiaProject/Celestia/releases

sburlot
Posts: 4
Joined: 25.11.2019
With us: 11 days 10 hours

Compile help?

Post #7by sburlot » 25.11.2019, 13:42

Hi,

When I try to compile Celestia/master, using Xcode 11.1 on MacOS 10.14.6, compilation stops with this error:

Code: Select all

make[2]: *** No rule to make target `/Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/OpenGL.framework', needed by `src/celestia/qt/celestia-qt'.  Stop.


1) no idea why I have Xcode-beta.app in the path
2) If I correct the paths in the CMakeFiles, I still have this error:

Code: Select all

ld: can't map file, errno=22 file '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenGL.framework' for architecture x86_64


Is there a way to compile Celestia on MacOS 10.14?
Did someone manage to make a valid Xcode project? The one included in the source is too old and needs a lot of changes.

Thanks,
Stephan

Markerz
Posts: 76
Joined: 29.01.2009
Age: 24
With us: 10 years 10 months
Location: Hangzhou, China

Post #8by Markerz » 26.11.2019, 08:37

sburlot wrote:Hi,

When I try to compile Celestia/master, using Xcode 11.1 on MacOS 10.14.6, compilation stops with this error:

Code: Select all

make[2]: *** No rule to make target `/Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/OpenGL.framework', needed by `src/celestia/qt/celestia-qt'.  Stop.



Hi

There is a bug with homebrew's bottled GLEW package, please rebuild and install glew from source. try this in command line

Code: Select all

brew reinstall glew --build-from-source


then regenerate your Xcode project file with cmake.


if there are further problems, let me know here :)

sburlot
Posts: 4
Joined: 25.11.2019
With us: 11 days 10 hours

Post #9by sburlot » 28.11.2019, 16:38

Hi,

reinstalling GLEW did the trick, thanks!

But now, how can I link against system libraries (or statically link with Homebrew libraries)?

Code: Select all

imac:build stephan$ otool -L celestia.app/Contents/MacOS/celestia-qt
celestia.app/Contents/MacOS/celestia-qt:
   /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1670.10.0)
   /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 1065.2.0)
   /usr/local/opt/gettext/lib/libintl.8.dylib (compatibility version 10.0.0, current version 10.6.0)
   /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0)
   /usr/local/opt/libpng/lib/libpng16.16.dylib (compatibility version 54.0.0, current version 54.0.0)
   /usr/local/opt/jpeg/lib/libjpeg.9.dylib (compatibility version 13.0.0, current version 13.0.0)
   /usr/local/opt/lua/lib/liblua.5.3.dylib (compatibility version 5.3.0, current version 5.3.5)
   /usr/local/opt/qt/lib/QtOpenGL.framework/Versions/5/QtOpenGL (compatibility version 5.13.0, current version 5.13.2)
   /usr/local/opt/qt/lib/QtWidgets.framework/Versions/5/QtWidgets (compatibility version 5.13.0, current version 5.13.2)
   /usr/local/opt/qt/lib/QtGui.framework/Versions/5/QtGui (compatibility version 5.13.0, current version 5.13.2)
   /usr/local/opt/qt/lib/QtCore.framework/Versions/5/QtCore (compatibility version 5.13.0, current version 5.13.2)
   /usr/local/opt/glew/lib/libGLEW.2.1.dylib (compatibility version 2.1.0, current version 2.1.0)
   /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11)
   /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 800.6.0)
   /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1281.0.0)


Code: Select all

then regenerate your Xcode project file with cmake.


You mean there's an option to use Xcode instead of all these CMake incantation? Can you show me how?

I tried to download the 1.6.2 release code, but the CMake install doesnt work and the Xcode project doesnt find some libraries (libintl.h for now)

Thanks a lot for your help!
Stephan

Markerz
Posts: 76
Joined: 29.01.2009
Age: 24
With us: 10 years 10 months
Location: Hangzhou, China

Post #10by Markerz » 29.11.2019, 07:00

sburlot wrote:reinstalling GLEW did the trick, thanks!

But now, how can I link against system libraries (or statically link with Homebrew libraries)?

You mean there's an option to use Xcode instead of all these CMake incantation? Can you show me how?

I tried to download the 1.6.2 release code, but the CMake install doesnt work and the Xcode project doesnt find some libraries (libintl.h for now)

For the master branch, the Xcode project in macosx folder does not work since it’s not maintained (I plan to replace it with a new implementation).

Linking to static library can be tricky since cmake locates the library for you, I haven’t tried it, but you can probably cmake -G Xcode and generate a Xcode project and edit configuration to make it work(replace dylib with a). But can I ask why are you trying to do that?

for 1.6.2 you should solely use the existing Xcode project in macosx folder. I did not upload the library and library header since they are third party ones, that’s why you found these things missing. If you need to have the files I can upload the files here.

But to bear in mind the two branches produce very different builds with regard to UI, master branch based on qt(cross platform) and 1.6.x based on bare Cocoa (more native UI)

sburlot
Posts: 4
Joined: 25.11.2019
With us: 11 days 10 hours

Post #11by sburlot » 03.12.2019, 10:19

Makerz wrote:for 1.6.2 you should solely use the existing Xcode project in macosx folder. I did not upload the library and library header since they are third party ones, that’s why you found these things missing. If you need to have the files I can upload the files here.

Thanks for the offer, I'll appreciate if you could post the needed files here.

Stephan

Markerz
Posts: 76
Joined: 29.01.2009
Age: 24
With us: 10 years 10 months
Location: Hangzhou, China

Post #12by Markerz » 03.12.2019, 12:09

@sburlot put it in the macosx folder and you should be able to build the 1.6.x branch, let me know whether it works for you or not :)
Attachments
additional.zip
(2.88 MiB) Downloaded 2 times

sburlot
Posts: 4
Joined: 25.11.2019
With us: 11 days 10 hours

Post #13by sburlot » 04.12.2019, 15:12

@Makerz

This time it compiles, but fails at the linking stage.
I have no idea where these 3 functions are defined. Are they part of Qt?

With what environment (Xcode, MacOS version) did you compile this app?

A big thank you for your help!

Code: Select all

Undefined symbols for architecture x86_64:
  "IsAbsolutePath(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)", referenced from:
      CelestiaCore::readFavoritesFile() in celestiacore.o
      CelestiaCore::writeFavoritesFile() in celestiacore.o
  "WriteableDataPath()", referenced from:
      CelestiaCore::readFavoritesFile() in celestiacore.o
      CelestiaCore::writeFavoritesFile() in celestiacore.o
  "MkDir(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)", referenced from:
      CelestiaCore::writeFavoritesFile() in celestiacore.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)


onetwothree
Developer
Posts: 340
Joined: 22.09.2018
With us: 1 year 2 months

Post #14by onetwothree » 04.12.2019, 18:56

Theae are from celutil/unixdirectory.cpp

Markerz
Posts: 76
Joined: 29.01.2009
Age: 24
With us: 10 years 10 months
Location: Hangzhou, China

Post #15by Markerz » 05.12.2019, 01:23

@sburlot are you using the Xcode project in the macosx folder from 1.6.x branch. Then it’s weird since unixdirectory.cpp is included and compiled as part of the project, this linking error shouldn’t have occurred.

Maybe try cleaning the project and rebuild it to see if it persists


Return to “Development”

Who is online