This value does not need to be set; it is determined by the application.
That the macosx_bundle target fails is a problem. This target needs to be
completely rewritten, but, it works for now.
What are you using to compile? How are you running? You need to start
posting more specific information.
In any case, you need to execute three targets: ALL_BUILD, install, and
macosx_bundle. Install puts the files relative to your build directory.
This is a Mac app, and /usr/local/anything would be inappropriate for
installing software. The install target creates a Stellarium.app in the
build directory.
The error you get is because the application can not find it's resources.
Setting STELROOT from the command line may work, but it will be better to
run it either as the app, or from Xcode, where the executable will be able
to find its resource.
On Sun, May 15, 2011 at 2:04 PM, rusirius <[email protected]>wrote:
>
> Having managed to set up my working development environment on the Mac,
> I am trying to compile my plugin. I have managed to compile Stellarium
> except for the last step:
>
> make macosx_bundle
>
> This doesent work and complains about there not being a rule:
>
> *** No rule to make target `CMakefiles/install.dir/all', needed by
> `CMakeFiles/macosx_bundle.dir/all'. Stop.
>
> Since I have already completed the 'make' and 'make install' I though it
> was Ok to proceed to compile the plugin anyway. However I am getting:
>
> Error: Undefined interface
>
> Usually this has indicated that the STELROOT varaible is not set.
> However I have set it and confirmed it is present when opening a
> terminal session. I initially tried to set it fist by using the usual
> Unix method:
>
> export STELROOT=/User/johnc/Prog/stellarium
>
> This didn't work. So after a biit of Googling I found that on a Mac one
> needs to edit the /etc/launch.conf. I did this and re-booted. Upon
> opening a terminal I checked to see whether STELROOT was present. It
> was. I did a make clean and a cmake ../.. and finally a make but still I
> get the same error.
>
> I noticed a reference to environment.plist as well but I'm not sure what
> the format of this file is as I can't find any examples. As I understand
> it however, launch.conf is supposed to add the enironment variable in
> 'all contexts' so I expected this to work.
>
> By the way, where does 'make install' place the files on a Mac? I was
> expecting them in /usr/local/stellarium but I can't find them anywhere?
> I should also point out that I'm not building Universal binaries as the
> long .configure line did not work on my Mac. In the end I had to compile
> libiconv and gettext with a default './configure'. I also had to change
> from the carbon to the cocoa flavour of QT as upon running the make
> script for Stellarium I got an error complaining that I was trying to
> compile a 64 bit application with a 32 bit version of QT.
>
>
>
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Stellarium-pubdevel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel
>
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Stellarium-pubdevel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel
