From: Fabien C. <fab...@go...> - 2009-04-28 16:59:29
|
Dear all, I am currently making tests on how to compile plugins as static, and distribute them linked together with Stellarium. I am almost there, and I had to make some little change to the plugin interface. So you may have to add a method in your plugin code.the method is virtual QString getPluginId() and it should simply return the name of the plugin, e.g. for VirGO it will be {return "VirGO";} Fabien |
From: Timothy R. <tr...@si...> - 2009-04-29 03:35:13
|
On Apr 28, 2009, at 11:59 AM, Fabien Chéreau wrote: > Dear all, > I am currently making tests on how to compile plugins as static, and > distribute them linked together with Stellarium. I am almost there, > and I had to make some little change to the plugin interface. So you > may have to add a method in your plugin code.the method is virtual > QString getPluginId() and it should simply return the name of the > plugin, e.g. for VirGO it will be {return "VirGO";} > Fabien What's the purpose of this? Does it allow some plugins to be static, and others dynamic? |
From: Fabien C. <fab...@go...> - 2009-04-29 06:38:40
|
On Wed, Apr 29, 2009 at 05:34, Timothy Reaves <tr...@si...> wrote: > > On Apr 28, 2009, at 11:59 AM, Fabien Chéreau wrote: > >> Dear all, >> I am currently making tests on how to compile plugins as static, and >> distribute them linked together with Stellarium. I am almost there, >> and I had to make some little change to the plugin interface. So you >> may have to add a method in your plugin code.the method is virtual >> QString getPluginId() and it should simply return the name of the >> plugin, e.g. for VirGO it will be {return "VirGO";} >> Fabien > > What's the purpose of this? Does it allow some plugins to be static, > and others dynamic? Yes, the updated code will first seach for a static plugin, and if not found will look through the dynamic ones. The main advantage of static plugins is that it solves all the problems of binary compatibility and version mismatch when distributing the packages on multiple plateform etc.. I think the best solution is to include statically all plugins which are mature enough with the next release. Another advantage is that currently when there is a link problem, the plugin fails at loading more or less silently, and it's a nightmare to debug. With static plugin you just see a normal link error. So it's also a good debugging tool. I will come back with instructions when I am done with a properly working example. Fabien |
From: Matthew G. <mat...@gm...> - 2009-04-29 12:16:57
|
On Tuesday 28 April 2009 17:59:23 Fabien Chéreau wrote: > Dear all, > I am currently making tests on how to compile plugins as static, and > distribute them linked together with Stellarium. I am almost there, > and I had to make some little change to the plugin interface. So you > may have to add a method in your plugin code.the method is virtual > QString getPluginId() and it should simply return the name of the > plugin, e.g. for VirGO it will be {return "VirGO";} Are you going to move the "stable" plugins inside the main Stellarium tree (i.e. so they can all be built with a single make command, and easier to package in with the main program)? If so, I would imagine VirGO will still remain in a separate tree? In any case, I think we should keep the HelloStelModule in the extmodules directory as an example to developers of 3rd party plugins. It might be worth keeping this as a minimalistic plugin, and adding a second example which adds a toolbar button and such. Matthew |
From: Fabien C. <fab...@go...> - 2009-04-29 13:15:04
|
Hi all, I just committed the first working static plugin based on VirGO!! :) I am going to migrate also HelloStelModule as an example and maybe other ones. Fabien On Wed, Apr 29, 2009 at 14:15, Matthew Gates <mat...@gm...> wrote: > On Tuesday 28 April 2009 17:59:23 Fabien Chéreau wrote: >> Dear all, >> I am currently making tests on how to compile plugins as static, and >> distribute them linked together with Stellarium. I am almost there, >> and I had to make some little change to the plugin interface. So you >> may have to add a method in your plugin code.the method is virtual >> QString getPluginId() and it should simply return the name of the >> plugin, e.g. for VirGO it will be {return "VirGO";} > > Are you going to move the "stable" plugins inside the main Stellarium tree > (i.e. so they can all be built with a single make command, and easier to > package in with the main program)? > > If so, I would imagine VirGO will still remain in a separate tree? > > In any case, I think we should keep the HelloStelModule in the extmodules > directory as an example to developers of 3rd party plugins. It might be > worth keeping this as a minimalistic plugin, and adding a second example > which adds a toolbar button and such. > > Matthew > > ------------------------------------------------------------------------------ > Register Now & Save for Velocity, the Web Performance & Operations > Conference from O'Reilly Media. Velocity features a full day of > expert-led, hands-on workshops and two days of sessions from industry > leaders in dedicated Performance & Operations tracks. Use code vel09scf > and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > > |
From: Fabien C. <fab...@go...> - 2009-04-29 14:32:37
|
I migrated HelloStelModule. So now the behaviour is the following: - When you compile a plugin, it will generate the static and the dynamic versions (e.g. libHelloStelModule.so and libHelloStelModule.a on linux). - Before compiling Stellarium, you need to indicate cmake that you want to use it as a staic plugin. For this set the USE_STATIC_PLUGIN_HELLOSTELMODULE to ON and enter the location of the .a library in the HELLOSTELMODULE_STATIC_PLUGIN_PATH variable. Stellarium should now link with the .a library. Finally to test, you also need to have the HelloStelModule directory in $HOME/.stellarium/modules so that Stellarium tries to load the plugin at start time. Cheers, Fabien On Wed, Apr 29, 2009 at 15:14, Fabien Chéreau <fab...@go...> wrote: > Hi all, > I just committed the first working static plugin based on VirGO!! :) I > am going to migrate also HelloStelModule as an example and maybe other > ones. > Fabien > > On Wed, Apr 29, 2009 at 14:15, Matthew Gates <mat...@gm...> wrote: >> On Tuesday 28 April 2009 17:59:23 Fabien Chéreau wrote: >>> Dear all, >>> I am currently making tests on how to compile plugins as static, and >>> distribute them linked together with Stellarium. I am almost there, >>> and I had to make some little change to the plugin interface. So you >>> may have to add a method in your plugin code.the method is virtual >>> QString getPluginId() and it should simply return the name of the >>> plugin, e.g. for VirGO it will be {return "VirGO";} >> >> Are you going to move the "stable" plugins inside the main Stellarium tree >> (i.e. so they can all be built with a single make command, and easier to >> package in with the main program)? >> >> If so, I would imagine VirGO will still remain in a separate tree? >> >> In any case, I think we should keep the HelloStelModule in the extmodules >> directory as an example to developers of 3rd party plugins. It might be >> worth keeping this as a minimalistic plugin, and adding a second example >> which adds a toolbar button and such. >> >> Matthew >> >> ------------------------------------------------------------------------------ >> Register Now & Save for Velocity, the Web Performance & Operations >> Conference from O'Reilly Media. Velocity features a full day of >> expert-led, hands-on workshops and two days of sessions from industry >> leaders in dedicated Performance & Operations tracks. Use code vel09scf >> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf >> _______________________________________________ >> Stellarium-pubdevel mailing list >> Ste...@li... >> https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel >> >> > |
From: Barry G. <bar...@ho...> - 2009-04-30 01:08:26
|
Hi Fabien I am intersted in compiling stellarium in Windows with the static module enabled but I have never been able to compile the VirGO module. I always have trouble with the Fits libraries. I think I have at last got them but the latest error concerns declaration long and long long in the fitsio.h file. and winnt.h files. What do I really need to compile the VirGo module in Windows. Barry Gerdes Beaumont Hills Observatory S 33' 41' 44" E 150' 56' 32" 12" F10 GPS Polar mounted Home Page http://www.geocities.com/barrykgerdes > Date: Wed, 29 Apr 2009 16:32:33 +0200 > From: fab...@go... > To: ste...@li... > Subject: Re: [Stellarium-pubdevel] Static plugin > > I migrated HelloStelModule. So now the behaviour is the following: > - When you compile a plugin, it will generate the static and the > dynamic versions (e.g. libHelloStelModule.so and libHelloStelModule.a > on linux). > - Before compiling Stellarium, you need to indicate cmake that you > want to use it as a staic plugin. For this set the > USE_STATIC_PLUGIN_HELLOSTELMODULE to ON and enter the location of the > .a library in the HELLOSTELMODULE_STATIC_PLUGIN_PATH variable. > > Stellarium should now link with the .a library. > Finally to test, you also need to have the HelloStelModule directory > in $HOME/.stellarium/modules so that Stellarium tries to load the > plugin at start time. > > Cheers, > Fabien > > On Wed, Apr 29, 2009 at 15:14, Fabien Chéreau > <fab...@go...> wrote: > > Hi all, > > I just committed the first working static plugin based on VirGO!! :) I > > am going to migrate also HelloStelModule as an example and maybe other > > ones. > > Fabien > > > > On Wed, Apr 29, 2009 at 14:15, Matthew Gates <mat...@gm...> wrote: > >> On Tuesday 28 April 2009 17:59:23 Fabien Chéreau wrote: > >>> Dear all, > >>> I am currently making tests on how to compile plugins as static, and > >>> distribute them linked together with Stellarium. I am almost there, > >>> and I had to make some little change to the plugin interface. So you > >>> may have to add a method in your plugin code.the method is virtual > >>> QString getPluginId() and it should simply return the name of the > >>> plugin, e.g. for VirGO it will be {return "VirGO";} > >> > >> Are you going to move the "stable" plugins inside the main Stellarium tree > >> (i.e. so they can all be built with a single make command, and easier to > >> package in with the main program)? > >> > >> If so, I would imagine VirGO will still remain in a separate tree? > >> > >> In any case, I think we should keep the HelloStelModule in the extmodules > >> directory as an example to developers of 3rd party plugins. It might be > >> worth keeping this as a minimalistic plugin, and adding a second example > >> which adds a toolbar button and such. > >> > >> Matthew > >> > >> ------------------------------------------------------------------------------ > >> Register Now & Save for Velocity, the Web Performance & Operations > >> Conference from O'Reilly Media. Velocity features a full day of > >> expert-led, hands-on workshops and two days of sessions from industry > >> leaders in dedicated Performance & Operations tracks. Use code vel09scf > >> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf > >> _______________________________________________ > >> Stellarium-pubdevel mailing list > >> Ste...@li... > >> https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > >> > >> > > > > ------------------------------------------------------------------------------ > Register Now & Save for Velocity, the Web Performance & Operations > Conference from O'Reilly Media. Velocity features a full day of > expert-led, hands-on workshops and two days of sessions from industry > leaders in dedicated Performance & Operations tracks. Use code vel09scf > and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel _________________________________________________________________ The new Windows Live Messenger has landed. Download it here. http://download.live.com/ |
From: Fabien C. <fab...@go...> - 2009-04-30 05:49:42
|
Hi Barry, Currently we are making some test on VirGO with other extra dependencies which are not very portable on windows (Tokyo Cabinet), so I am not sure it's the best time to attempt windows compilation.. Fabien On Thu, Apr 30, 2009 at 03:06, Barry Gerdes <bar...@ho...> wrote: > Hi Fabien > > I am intersted in compiling stellarium in Windows with the static module > enabled but I have never been able to compile the VirGO module. I always > have trouble with the Fits libraries. I think I have at last got them but > the latest error concerns declaration long and long long in the fitsio.h > file. and winnt.h files. What do I really need to compile the VirGo module > in Windows. > > > Barry Gerdes > Beaumont Hills Observatory > S 33' 41' 44" E 150' 56' 32" > 12" F10 GPS Polar mounted > Home Page http://www.geocities.com/barrykgerdes > > > > >> Date: Wed, 29 Apr 2009 16:32:33 +0200 >> From: fab...@go... >> To: ste...@li... >> Subject: Re: [Stellarium-pubdevel] Static plugin >> >> I migrated HelloStelModule. So now the behaviour is the following: >> - When you compile a plugin, it will generate the static and the >> dynamic versions (e.g. libHelloStelModule.so and libHelloStelModule.a >> on linux). >> - Before compiling Stellarium, you need to indicate cmake that you >> want to use it as a staic plugin. For this set the >> USE_STATIC_PLUGIN_HELLOSTELMODULE to ON and enter the location of the >> .a library in the HELLOSTELMODULE_STATIC_PLUGIN_PATH variable. >> >> Stellarium should now link with the .a library. >> Finally to test, you also need to have the HelloStelModule directory >> in $HOME/.stellarium/modules so that Stellarium tries to load the >> plugin at start time. >> >> Cheers, >> Fabien >> >> On Wed, Apr 29, 2009 at 15:14, Fabien Chéreau >> <fab...@go...> wrote: >> > Hi all, >> > I just committed the first working static plugin based on VirGO!! :) I >> > am going to migrate also HelloStelModule as an example and maybe other >> > ones. >> > Fabien >> > >> > On Wed, Apr 29, 2009 at 14:15, Matthew Gates <mat...@gm...> >> > wrote: >> >> On Tuesday 28 April 2009 17:59:23 Fabien Chéreau wrote: >> >>> Dear all, >> >>> I am currently making tests on how to compile plugins as static, and >> >>> distribute them linked together with Stellarium. I am almost there, >> >>> and I had to make some little change to the plugin interface. So you >> >>> may have to add a method in your plugin code.the method is virtual >> >>> QString getPluginId() and it should simply return the name of the >> >>> plugin, e.g. for VirGO it will be {return "VirGO";} >> >> >> >> Are you going to move the "stable" plugins inside the main Stellarium >> >> tree >> >> (i.e. so they can all be built with a single make command, and easier >> >> to >> >> package in with the main program)? >> >> >> >> If so, I would imagine VirGO will still remain in a separate tree? >> >> >> >> In any case, I think we should keep the HelloStelModule in the >> >> extmodules >> >> directory as an example to developers of 3rd party plugins. It might >> >> be >> >> worth keeping this as a minimalistic plugin, and adding a second >> >> example >> >> which adds a toolbar button and such. >> >> >> >> Matthew >> >> |
From: Barry G. <bar...@ho...> - 2009-04-30 12:39:10
|
Thanks Fabien I was just wondering whether I could compile it. I saw that dependancy on tokio cabinet but it disappeared when I got the libcfits installed. I will have a go on Linux and see what happens. I need the fits libraries there too. Barry Gerdes Beaumont Hills Observatory S 33' 41' 44" E 150' 56' 32" 12" F10 GPS Polar mounted Home Page http://www.geocities.com/barrykgerdes > Date: Thu, 30 Apr 2009 07:49:39 +0200 > From: fab...@go... > To: ste...@li... > Subject: Re: [Stellarium-pubdevel] Static plugin > > Hi Barry, > Currently we are making some test on VirGO with other extra > dependencies which are not very portable on windows (Tokyo Cabinet), > so I am not sure it's the best time to attempt windows compilation.. > Fabien > > On Thu, Apr 30, 2009 at 03:06, Barry Gerdes <bar...@ho...> wrote: > > Hi Fabien > > > > I am intersted in compiling stellarium in Windows with the static module > > enabled but I have never been able to compile the VirGO module. I always > > have trouble with the Fits libraries. I think I have at last got them but > > the latest error concerns declaration long and long long in the fitsio.h > > file. and winnt.h files. What do I really need to compile the VirGo module > > in Windows. > > > > > > Barry Gerdes > > Beaumont Hills Observatory > > S 33' 41' 44" E 150' 56' 32" > > 12" F10 GPS Polar mounted > > Home Page http://www.geocities.com/barrykgerdes > > > > > > > > > >> Date: Wed, 29 Apr 2009 16:32:33 +0200 > >> From: fab...@go... > >> To: ste...@li... > >> Subject: Re: [Stellarium-pubdevel] Static plugin > >> > >> I migrated HelloStelModule. So now the behaviour is the following: > >> - When you compile a plugin, it will generate the static and the > >> dynamic versions (e.g. libHelloStelModule.so and libHelloStelModule.a > >> on linux). > >> - Before compiling Stellarium, you need to indicate cmake that you > >> want to use it as a staic plugin. For this set the > >> USE_STATIC_PLUGIN_HELLOSTELMODULE to ON and enter the location of the > >> .a library in the HELLOSTELMODULE_STATIC_PLUGIN_PATH variable. > >> > >> Stellarium should now link with the .a library. > >> Finally to test, you also need to have the HelloStelModule directory > >> in $HOME/.stellarium/modules so that Stellarium tries to load the > >> plugin at start time. > >> > >> Cheers, > >> Fabien > >> > >> On Wed, Apr 29, 2009 at 15:14, Fabien Chéreau > >> <fab...@go...> wrote: > >> > Hi all, > >> > I just committed the first working static plugin based on VirGO!! :) I > >> > am going to migrate also HelloStelModule as an example and maybe other > >> > ones. > >> > Fabien > >> > > >> > On Wed, Apr 29, 2009 at 14:15, Matthew Gates <mat...@gm...> > >> > wrote: > >> >> On Tuesday 28 April 2009 17:59:23 Fabien Chéreau wrote: > >> >>> Dear all, > >> >>> I am currently making tests on how to compile plugins as static, and > >> >>> distribute them linked together with Stellarium. I am almost there, > >> >>> and I had to make some little change to the plugin interface. So you > >> >>> may have to add a method in your plugin code.the method is virtual > >> >>> QString getPluginId() and it should simply return the name of the > >> >>> plugin, e.g. for VirGO it will be {return "VirGO";} > >> >> > >> >> Are you going to move the "stable" plugins inside the main Stellarium > >> >> tree > >> >> (i.e. so they can all be built with a single make command, and easier > >> >> to > >> >> package in with the main program)? > >> >> > >> >> If so, I would imagine VirGO will still remain in a separate tree? > >> >> > >> >> In any case, I think we should keep the HelloStelModule in the > >> >> extmodules > >> >> directory as an example to developers of 3rd party plugins. It might > >> >> be > >> >> worth keeping this as a minimalistic plugin, and adding a second > >> >> example > >> >> which adds a toolbar button and such. > >> >> > >> >> Matthew > >> >> > > ------------------------------------------------------------------------------ > Register Now & Save for Velocity, the Web Performance & Operations > Conference from O'Reilly Media. Velocity features a full day of > expert-led, hands-on workshops and two days of sessions from industry > leaders in dedicated Performance & Operations tracks. Use code vel09scf > and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel _________________________________________________________________ Looking to change your car this year? Find car news, reviews and more http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fsecure%2Dau%2Eimrworldwide%2Ecom%2Fcgi%2Dbin%2Fa%2Fci%5F450304%2Fet%5F2%2Fcg%5F801459%2Fpi%5F1004813%2Fai%5F859641&_t=762955845&_r=tig_OCT07&_m=EXT |