From: Bogdan M. <dag...@gm...> - 2010-03-17 11:44:57
|
Hello. As reported by Barry Gerdes, there's a problem with the dynamic plug-ins on Windows. If the plug-in contains some references to Stellarium's GUI, a linker error is thrown: D:\Qt\2010.02.1\mingw\bin\g++.exe -enable-runtime-pseudo-reloc -Wl,--allow-multiple-definition -shared -o libExampleDialog.dll -Wl,--major-image-version,0,--minor-image-version,0 CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj CMakeFiles\ExampleDialog.dir\gui\ExampleDialogWindow.cpp.obj CMakeFiles\ExampleDialog.dir\gui\StelDialogExampleDialog.cpp.obj CMakeFiles\ExampleDialog.dir\gui\moc_StelDialogExampleDialog.cxx.obj CMakeFiles\ExampleDialog.dir\gui\moc_ExampleDialogWindow.cxx.obj CMakeFiles\ExampleDialog.dir\moc_ExampleDialog.cxx.obj CMakeFiles\ExampleDialog.dir\qrc_exampleDialog.cxx.obj -LD:\stellarium\stellarium\builds\msys\src -lstelMain D:\Qt\2010.02.1\qt\lib\libQtOpenGLd4.a -lopengl32 -lglu32 -lgdi32 -luser32 D:\Qt\2010.02.1\qt\lib\libQtGuid4.a -limm32 -lwinmm D:\Qt\2010.02.1\qt\lib\libQtNetworkd4.a D:\Qt\2010.02.1\qt\lib\libQtCored4.a -lws2_32 -lglu32 -lopengl32 -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 Info: resolving vtable for StelModule by linking to __imp___ZTV10StelModule (auto-import) Info: resolving StelApp::singleton by linking to __imp___ZN7StelApp9singletonE (auto-import) Info: resolving StelMainGraphicsView::singleton by linking to __imp___ZN20StelMainGraphicsView9singletonE (auto-import) mingw32-make[2]: Leaving directory `D:/stellarium/extmodules/ExampleDialog/builds/msys' mingw32-make[1]: Leaving directory `D:/stellarium/extmodules/ExampleDialog/builds/msys' d:/qt/2010.02.1/mingw/bin/../lib/gcc/mingw32/4.4.0/../../../../mingw32/bin/ld.exe: warning: auto-importing has been activated without --enable-auto-import specified on the command line. This should work unless it involves constant data structures referencing symbols from auto-imported DLLs. CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj:D:/stellarium/extmodules/ExampleDialog/src/ExampleDialog.cpp:98: undefined reference to `StelButton::StelButton(QGraphicsItem*, QPixmap const&, QPixmap const&, QPixmap const&, QAction*, bool)' CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj:D:/stellarium/extmodules/ExampleDialog/src/ExampleDialog.cpp:99: undefined reference to `StelGui::getButtonBar()' CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj:D:/stellarium/extmodules/ExampleDialog/src/ExampleDialog.cpp:99: undefined reference to `BottomStelBar::addButton(StelButton*, QString const&, QString const&)' CMakeFiles\ExampleDialog.dir\gui\ExampleDialogWindow.cpp.obj:ExampleDialogWindow.cpp:(.text$_ZN8BarFrameC1EP7QWidget[BarFrame::BarFrame(QWidget*)]+0x39): undefined reference to `vtable for BarFrame' CMakeFiles\ExampleDialog.dir\gui\ExampleDialogWindow.cpp.obj:ExampleDialogWindow.cpp:(.text$_ZN8BarFrameC1EP7QWidget[BarFrame::BarFrame(QWidget*)]+0x43): undefined reference to `vtable for BarFrame' collect2: ld returned 1 exit status mingw32-make[2]: *** [src/libExampleDialog.dll] Error 1 mingw32-make[1]: *** [src/CMakeFiles/ExampleDialog.dir/all] Error 2 mingw32-make: *** [all] Error 2 Exited with code 2. Error while building project ExampleDialog When executing build step 'Make' Both KeyBundings and ExampleDialog are affected, which is normal, as the former is based on the latter. Could someone help me with this, please? This effectively limits plug-in development on Windows. Regards, Bogdan Marinov |
From: Bogdan M. <dag...@gm...> - 2010-03-24 23:09:08
|
On Wed, Mar 17, 2010 at 1:44 PM, Bogdan Marinov <dag...@gm...> wrote: > Hello. > > As reported by Barry Gerdes, there's a problem with the dynamic > plug-ins on Windows. If the plug-in contains some references to > Stellarium's GUI, a linker error is thrown: > > D:\Qt\2010.02.1\mingw\bin\g++.exe -enable-runtime-pseudo-reloc > -Wl,--allow-multiple-definition -shared -o libExampleDialog.dll > -Wl,--major-image-version,0,--minor-image-version,0 > CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj > CMakeFiles\ExampleDialog.dir\gui\ExampleDialogWindow.cpp.obj > CMakeFiles\ExampleDialog.dir\gui\StelDialogExampleDialog.cpp.obj > CMakeFiles\ExampleDialog.dir\gui\moc_StelDialogExampleDialog.cxx.obj > CMakeFiles\ExampleDialog.dir\gui\moc_ExampleDialogWindow.cxx.obj > CMakeFiles\ExampleDialog.dir\moc_ExampleDialog.cxx.obj > CMakeFiles\ExampleDialog.dir\qrc_exampleDialog.cxx.obj > -LD:\stellarium\stellarium\builds\msys\src -lstelMain > D:\Qt\2010.02.1\qt\lib\libQtOpenGLd4.a -lopengl32 -lglu32 -lgdi32 > -luser32 D:\Qt\2010.02.1\qt\lib\libQtGuid4.a -limm32 -lwinmm > D:\Qt\2010.02.1\qt\lib\libQtNetworkd4.a > D:\Qt\2010.02.1\qt\lib\libQtCored4.a -lws2_32 -lglu32 -lopengl32 > -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 > -luuid -lcomdlg32 -ladvapi32 > Info: resolving vtable for StelModule by linking to > __imp___ZTV10StelModule (auto-import) > Info: resolving StelApp::singleton by linking to > __imp___ZN7StelApp9singletonE (auto-import) > Info: resolving StelMainGraphicsView::singleton by linking to > __imp___ZN20StelMainGraphicsView9singletonE (auto-import) > mingw32-make[2]: Leaving directory > `D:/stellarium/extmodules/ExampleDialog/builds/msys' > mingw32-make[1]: Leaving directory > `D:/stellarium/extmodules/ExampleDialog/builds/msys' > d:/qt/2010.02.1/mingw/bin/../lib/gcc/mingw32/4.4.0/../../../../mingw32/bin/ld.exe: > warning: auto-importing has been activated without > --enable-auto-import specified on the command line. > This should work unless it involves constant data structures > referencing symbols from auto-imported DLLs. > CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj:D:/stellarium/extmodules/ExampleDialog/src/ExampleDialog.cpp:98: > undefined reference to `StelButton::StelButton(QGraphicsItem*, QPixmap > const&, QPixmap const&, QPixmap const&, QAction*, bool)' > CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj:D:/stellarium/extmodules/ExampleDialog/src/ExampleDialog.cpp:99: > undefined reference to `StelGui::getButtonBar()' > CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj:D:/stellarium/extmodules/ExampleDialog/src/ExampleDialog.cpp:99: > undefined reference to `BottomStelBar::addButton(StelButton*, QString > const&, QString const&)' > CMakeFiles\ExampleDialog.dir\gui\ExampleDialogWindow.cpp.obj:ExampleDialogWindow.cpp:(.text$_ZN8BarFrameC1EP7QWidget[BarFrame::BarFrame(QWidget*)]+0x39): > undefined reference to `vtable for BarFrame' > CMakeFiles\ExampleDialog.dir\gui\ExampleDialogWindow.cpp.obj:ExampleDialogWindow.cpp:(.text$_ZN8BarFrameC1EP7QWidget[BarFrame::BarFrame(QWidget*)]+0x43): > undefined reference to `vtable for BarFrame' > collect2: ld returned 1 exit status > mingw32-make[2]: *** [src/libExampleDialog.dll] Error 1 > mingw32-make[1]: *** [src/CMakeFiles/ExampleDialog.dir/all] Error 2 > mingw32-make: *** [all] Error 2 > Exited with code 2. > Error while building project ExampleDialog > When executing build step 'Make' > > Both KeyBundings and ExampleDialog are affected, which is normal, as > the former is based on the latter. > > Could someone help me with this, please? This effectively limits > plug-in development on Windows. I've made a few futile attempts at solving this today. It seems that it is impossible to link to any classes in the GUI (e.g. StelButton, BarFrame, StelDialog). Am I missing something obvious? Bogdan |
From: Bogdan M. <dag...@gm...> - 2010-03-25 11:59:20
|
On Thu, Mar 25, 2010 at 1:08 AM, Bogdan Marinov <dag...@gm...> wrote: > On Wed, Mar 17, 2010 at 1:44 PM, Bogdan Marinov <dag...@gm...> wrote: >> Hello. >> >> As reported by Barry Gerdes, there's a problem with the dynamic >> plug-ins on Windows. If the plug-in contains some references to >> Stellarium's GUI, a linker error is thrown: >> >> D:\Qt\2010.02.1\mingw\bin\g++.exe -enable-runtime-pseudo-reloc >> -Wl,--allow-multiple-definition -shared -o libExampleDialog.dll >> -Wl,--major-image-version,0,--minor-image-version,0 >> CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj >> CMakeFiles\ExampleDialog.dir\gui\ExampleDialogWindow.cpp.obj >> CMakeFiles\ExampleDialog.dir\gui\StelDialogExampleDialog.cpp.obj >> CMakeFiles\ExampleDialog.dir\gui\moc_StelDialogExampleDialog.cxx.obj >> CMakeFiles\ExampleDialog.dir\gui\moc_ExampleDialogWindow.cxx.obj >> CMakeFiles\ExampleDialog.dir\moc_ExampleDialog.cxx.obj >> CMakeFiles\ExampleDialog.dir\qrc_exampleDialog.cxx.obj >> -LD:\stellarium\stellarium\builds\msys\src -lstelMain >> D:\Qt\2010.02.1\qt\lib\libQtOpenGLd4.a -lopengl32 -lglu32 -lgdi32 >> -luser32 D:\Qt\2010.02.1\qt\lib\libQtGuid4.a -limm32 -lwinmm >> D:\Qt\2010.02.1\qt\lib\libQtNetworkd4.a >> D:\Qt\2010.02.1\qt\lib\libQtCored4.a -lws2_32 -lglu32 -lopengl32 >> -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 >> -luuid -lcomdlg32 -ladvapi32 >> Info: resolving vtable for StelModule by linking to >> __imp___ZTV10StelModule (auto-import) >> Info: resolving StelApp::singleton by linking to >> __imp___ZN7StelApp9singletonE (auto-import) >> Info: resolving StelMainGraphicsView::singleton by linking to >> __imp___ZN20StelMainGraphicsView9singletonE (auto-import) >> mingw32-make[2]: Leaving directory >> `D:/stellarium/extmodules/ExampleDialog/builds/msys' >> mingw32-make[1]: Leaving directory >> `D:/stellarium/extmodules/ExampleDialog/builds/msys' >> d:/qt/2010.02.1/mingw/bin/../lib/gcc/mingw32/4.4.0/../../../../mingw32/bin/ld.exe: >> warning: auto-importing has been activated without >> --enable-auto-import specified on the command line. >> This should work unless it involves constant data structures >> referencing symbols from auto-imported DLLs. >> CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj:D:/stellarium/extmodules/ExampleDialog/src/ExampleDialog.cpp:98: >> undefined reference to `StelButton::StelButton(QGraphicsItem*, QPixmap >> const&, QPixmap const&, QPixmap const&, QAction*, bool)' >> CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj:D:/stellarium/extmodules/ExampleDialog/src/ExampleDialog.cpp:99: >> undefined reference to `StelGui::getButtonBar()' >> CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj:D:/stellarium/extmodules/ExampleDialog/src/ExampleDialog.cpp:99: >> undefined reference to `BottomStelBar::addButton(StelButton*, QString >> const&, QString const&)' >> CMakeFiles\ExampleDialog.dir\gui\ExampleDialogWindow.cpp.obj:ExampleDialogWindow.cpp:(.text$_ZN8BarFrameC1EP7QWidget[BarFrame::BarFrame(QWidget*)]+0x39): >> undefined reference to `vtable for BarFrame' >> CMakeFiles\ExampleDialog.dir\gui\ExampleDialogWindow.cpp.obj:ExampleDialogWindow.cpp:(.text$_ZN8BarFrameC1EP7QWidget[BarFrame::BarFrame(QWidget*)]+0x43): >> undefined reference to `vtable for BarFrame' >> collect2: ld returned 1 exit status >> mingw32-make[2]: *** [src/libExampleDialog.dll] Error 1 >> mingw32-make[1]: *** [src/CMakeFiles/ExampleDialog.dir/all] Error 2 >> mingw32-make: *** [all] Error 2 >> Exited with code 2. >> Error while building project ExampleDialog >> When executing build step 'Make' >> >> Both KeyBundings and ExampleDialog are affected, which is normal, as >> the former is based on the latter. >> >> Could someone help me with this, please? This effectively limits >> plug-in development on Windows. > > I've made a few futile attempts at solving this today. It seems that > it is impossible to link to any classes in the GUI (e.g. StelButton, > BarFrame, StelDialog). Am I missing something obvious? Some progress: I used dlltool to extract a list of all symbols exported by libstelMain.dll and it seems that none of the GUI classes are exported. http://mingw.org/wiki/CreateImportLibraries I've tried forcing an export before, but it didn't work. I'll try again in some other way. Bogdan |
From: Bogdan M. <dag...@gm...> - 2010-03-26 17:21:14
|
On Fri, Mar 26, 2010 at 4:35 PM, Fabien Chéreau <fab...@go...> wrote: > Nice :) > By the way Bogdan, if you wish and have time for that you can try to > organize/create the release yourself. Currently it was always me or > Matthew, but we are quite busy in the next weeks. And it's always good > for the project that some new people do that :) I'm not thrilled by the idea. :) I don't have much time, either - I just wanted to get this issue fixed, because it interfered with my work on the new telescope control plug-in. (Which can be done in smaller steps over time.) I can help with some of the organisation, but my computer is not very suitable for a release. Compilation, especially on Windows, is painfully slow, and I haven't tried to create an installer for some time. Regards, Bogdan Marinov |
From: <ha...@la...> - 2010-03-26 19:44:33
|
-just breaking in on this thread- Bogdan Marinov wrote on 20100326: ... > computer is not very > suitable for a release. Compilation, especially on Windows, is > painfully slow, and I haven't tried to create an installer for some > time. This process is scriptable. I'm still looking for a MS-Windows and a MacOSX buildbot host so that we can automatically generate stellarium installers per commit. If you think this is worthwhile to persue of course. -- Hans Lambermont |
From: Bogdan M. <dag...@gm...> - 2010-03-25 12:56:23
|
On Thu, Mar 25, 2010 at 1:59 PM, Bogdan Marinov <dag...@gm...> wrote: > On Thu, Mar 25, 2010 at 1:08 AM, Bogdan Marinov <dag...@gm...> wrote: >> On Wed, Mar 17, 2010 at 1:44 PM, Bogdan Marinov <dag...@gm...> wrote: >>> Hello. >>> >>> As reported by Barry Gerdes, there's a problem with the dynamic >>> plug-ins on Windows. If the plug-in contains some references to >>> Stellarium's GUI, a linker error is thrown: >>> >>> D:\Qt\2010.02.1\mingw\bin\g++.exe -enable-runtime-pseudo-reloc >>> -Wl,--allow-multiple-definition -shared -o libExampleDialog.dll >>> -Wl,--major-image-version,0,--minor-image-version,0 >>> CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj >>> CMakeFiles\ExampleDialog.dir\gui\ExampleDialogWindow.cpp.obj >>> CMakeFiles\ExampleDialog.dir\gui\StelDialogExampleDialog.cpp.obj >>> CMakeFiles\ExampleDialog.dir\gui\moc_StelDialogExampleDialog.cxx.obj >>> CMakeFiles\ExampleDialog.dir\gui\moc_ExampleDialogWindow.cxx.obj >>> CMakeFiles\ExampleDialog.dir\moc_ExampleDialog.cxx.obj >>> CMakeFiles\ExampleDialog.dir\qrc_exampleDialog.cxx.obj >>> -LD:\stellarium\stellarium\builds\msys\src -lstelMain >>> D:\Qt\2010.02.1\qt\lib\libQtOpenGLd4.a -lopengl32 -lglu32 -lgdi32 >>> -luser32 D:\Qt\2010.02.1\qt\lib\libQtGuid4.a -limm32 -lwinmm >>> D:\Qt\2010.02.1\qt\lib\libQtNetworkd4.a >>> D:\Qt\2010.02.1\qt\lib\libQtCored4.a -lws2_32 -lglu32 -lopengl32 >>> -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 >>> -luuid -lcomdlg32 -ladvapi32 >>> Info: resolving vtable for StelModule by linking to >>> __imp___ZTV10StelModule (auto-import) >>> Info: resolving StelApp::singleton by linking to >>> __imp___ZN7StelApp9singletonE (auto-import) >>> Info: resolving StelMainGraphicsView::singleton by linking to >>> __imp___ZN20StelMainGraphicsView9singletonE (auto-import) >>> mingw32-make[2]: Leaving directory >>> `D:/stellarium/extmodules/ExampleDialog/builds/msys' >>> mingw32-make[1]: Leaving directory >>> `D:/stellarium/extmodules/ExampleDialog/builds/msys' >>> d:/qt/2010.02.1/mingw/bin/../lib/gcc/mingw32/4.4.0/../../../../mingw32/bin/ld.exe: >>> warning: auto-importing has been activated without >>> --enable-auto-import specified on the command line. >>> This should work unless it involves constant data structures >>> referencing symbols from auto-imported DLLs. >>> CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj:D:/stellarium/extmodules/ExampleDialog/src/ExampleDialog.cpp:98: >>> undefined reference to `StelButton::StelButton(QGraphicsItem*, QPixmap >>> const&, QPixmap const&, QPixmap const&, QAction*, bool)' >>> CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj:D:/stellarium/extmodules/ExampleDialog/src/ExampleDialog.cpp:99: >>> undefined reference to `StelGui::getButtonBar()' >>> CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj:D:/stellarium/extmodules/ExampleDialog/src/ExampleDialog.cpp:99: >>> undefined reference to `BottomStelBar::addButton(StelButton*, QString >>> const&, QString const&)' >>> CMakeFiles\ExampleDialog.dir\gui\ExampleDialogWindow.cpp.obj:ExampleDialogWindow.cpp:(.text$_ZN8BarFrameC1EP7QWidget[BarFrame::BarFrame(QWidget*)]+0x39): >>> undefined reference to `vtable for BarFrame' >>> CMakeFiles\ExampleDialog.dir\gui\ExampleDialogWindow.cpp.obj:ExampleDialogWindow.cpp:(.text$_ZN8BarFrameC1EP7QWidget[BarFrame::BarFrame(QWidget*)]+0x43): >>> undefined reference to `vtable for BarFrame' >>> collect2: ld returned 1 exit status >>> mingw32-make[2]: *** [src/libExampleDialog.dll] Error 1 >>> mingw32-make[1]: *** [src/CMakeFiles/ExampleDialog.dir/all] Error 2 >>> mingw32-make: *** [all] Error 2 >>> Exited with code 2. >>> Error while building project ExampleDialog >>> When executing build step 'Make' >>> >>> Both KeyBundings and ExampleDialog are affected, which is normal, as >>> the former is based on the latter. >>> >>> Could someone help me with this, please? This effectively limits >>> plug-in development on Windows. >> >> I've made a few futile attempts at solving this today. It seems that >> it is impossible to link to any classes in the GUI (e.g. StelButton, >> BarFrame, StelDialog). Am I missing something obvious? > > Some progress: I used dlltool to extract a list of all symbols > exported by libstelMain.dll and it seems that none of the GUI classes > are exported. > http://mingw.org/wiki/CreateImportLibraries > > I've tried forcing an export before, but it didn't work. I'll try > again in some other way. Mystery solved: the GUI is included with the rest of the static plug-ins in stellarium.exe. Let's see if I can get the plug-in to link to it... Bogdan |
From: Fabien C. <fab...@go...> - 2010-03-25 13:26:48
|
Ah now I know! There was the same problem in win32 before which is the reason I had to create the libStelMain.dll instead of linking everything in stellarium.exe Now in the last release I made the GUI a static library linked with stellarium.exe and forgot to code the case where GENERATE_STELMAINLIB is defined. In this case the GUI code sjould be linked in libsteMain.dll instead. Thanks Bogdan, I let you trying to deal with that (I don't have my windows machine at the moment). Let me know if you find a way to fix that. Fabien On Thu, Mar 25, 2010 at 13:56, Bogdan Marinov <dag...@gm...> wrote: > On Thu, Mar 25, 2010 at 1:59 PM, Bogdan Marinov <dag...@gm...> wrote: >> On Thu, Mar 25, 2010 at 1:08 AM, Bogdan Marinov <dag...@gm...> wrote: >>> On Wed, Mar 17, 2010 at 1:44 PM, Bogdan Marinov <dag...@gm...> wrote: >>>> Hello. >>>> >>>> As reported by Barry Gerdes, there's a problem with the dynamic >>>> plug-ins on Windows. If the plug-in contains some references to >>>> Stellarium's GUI, a linker error is thrown: >>>> >>>> D:\Qt\2010.02.1\mingw\bin\g++.exe -enable-runtime-pseudo-reloc >>>> -Wl,--allow-multiple-definition -shared -o libExampleDialog.dll >>>> -Wl,--major-image-version,0,--minor-image-version,0 >>>> CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj >>>> CMakeFiles\ExampleDialog.dir\gui\ExampleDialogWindow.cpp.obj >>>> CMakeFiles\ExampleDialog.dir\gui\StelDialogExampleDialog.cpp.obj >>>> CMakeFiles\ExampleDialog.dir\gui\moc_StelDialogExampleDialog.cxx.obj >>>> CMakeFiles\ExampleDialog.dir\gui\moc_ExampleDialogWindow.cxx.obj >>>> CMakeFiles\ExampleDialog.dir\moc_ExampleDialog.cxx.obj >>>> CMakeFiles\ExampleDialog.dir\qrc_exampleDialog.cxx.obj >>>> -LD:\stellarium\stellarium\builds\msys\src -lstelMain >>>> D:\Qt\2010.02.1\qt\lib\libQtOpenGLd4.a -lopengl32 -lglu32 -lgdi32 >>>> -luser32 D:\Qt\2010.02.1\qt\lib\libQtGuid4.a -limm32 -lwinmm >>>> D:\Qt\2010.02.1\qt\lib\libQtNetworkd4.a >>>> D:\Qt\2010.02.1\qt\lib\libQtCored4.a -lws2_32 -lglu32 -lopengl32 >>>> -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 >>>> -luuid -lcomdlg32 -ladvapi32 >>>> Info: resolving vtable for StelModule by linking to >>>> __imp___ZTV10StelModule (auto-import) >>>> Info: resolving StelApp::singleton by linking to >>>> __imp___ZN7StelApp9singletonE (auto-import) >>>> Info: resolving StelMainGraphicsView::singleton by linking to >>>> __imp___ZN20StelMainGraphicsView9singletonE (auto-import) >>>> mingw32-make[2]: Leaving directory >>>> `D:/stellarium/extmodules/ExampleDialog/builds/msys' >>>> mingw32-make[1]: Leaving directory >>>> `D:/stellarium/extmodules/ExampleDialog/builds/msys' >>>> d:/qt/2010.02.1/mingw/bin/../lib/gcc/mingw32/4.4.0/../../../../mingw32/bin/ld.exe: >>>> warning: auto-importing has been activated without >>>> --enable-auto-import specified on the command line. >>>> This should work unless it involves constant data structures >>>> referencing symbols from auto-imported DLLs. >>>> CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj:D:/stellarium/extmodules/ExampleDialog/src/ExampleDialog.cpp:98: >>>> undefined reference to `StelButton::StelButton(QGraphicsItem*, QPixmap >>>> const&, QPixmap const&, QPixmap const&, QAction*, bool)' >>>> CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj:D:/stellarium/extmodules/ExampleDialog/src/ExampleDialog.cpp:99: >>>> undefined reference to `StelGui::getButtonBar()' >>>> CMakeFiles\ExampleDialog.dir\ExampleDialog.cpp.obj:D:/stellarium/extmodules/ExampleDialog/src/ExampleDialog.cpp:99: >>>> undefined reference to `BottomStelBar::addButton(StelButton*, QString >>>> const&, QString const&)' >>>> CMakeFiles\ExampleDialog.dir\gui\ExampleDialogWindow.cpp.obj:ExampleDialogWindow.cpp:(.text$_ZN8BarFrameC1EP7QWidget[BarFrame::BarFrame(QWidget*)]+0x39): >>>> undefined reference to `vtable for BarFrame' >>>> CMakeFiles\ExampleDialog.dir\gui\ExampleDialogWindow.cpp.obj:ExampleDialogWindow.cpp:(.text$_ZN8BarFrameC1EP7QWidget[BarFrame::BarFrame(QWidget*)]+0x43): >>>> undefined reference to `vtable for BarFrame' >>>> collect2: ld returned 1 exit status >>>> mingw32-make[2]: *** [src/libExampleDialog.dll] Error 1 >>>> mingw32-make[1]: *** [src/CMakeFiles/ExampleDialog.dir/all] Error 2 >>>> mingw32-make: *** [all] Error 2 >>>> Exited with code 2. >>>> Error while building project ExampleDialog >>>> When executing build step 'Make' >>>> >>>> Both KeyBundings and ExampleDialog are affected, which is normal, as >>>> the former is based on the latter. >>>> >>>> Could someone help me with this, please? This effectively limits >>>> plug-in development on Windows. >>> >>> I've made a few futile attempts at solving this today. It seems that >>> it is impossible to link to any classes in the GUI (e.g. StelButton, >>> BarFrame, StelDialog). Am I missing something obvious? >> >> Some progress: I used dlltool to extract a list of all symbols >> exported by libstelMain.dll and it seems that none of the GUI classes >> are exported. >> http://mingw.org/wiki/CreateImportLibraries >> >> I've tried forcing an export before, but it didn't work. I'll try >> again in some other way. > > Mystery solved: the GUI is included with the rest of the static > plug-ins in stellarium.exe. > > Let's see if I can get the plug-in to link to it... > > Bogdan > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > |
From: Bogdan M. <dag...@gm...> - 2010-03-26 19:47:43
|
On Fri, Mar 26, 2010 at 9:44 PM, H <ha...@la...> wrote: > -just breaking in on this thread- > > Bogdan Marinov wrote on 20100326: > ... >> computer is not very >> suitable for a release. Compilation, especially on Windows, is >> painfully slow, and I haven't tried to create an installer for some >> time. > > This process is scriptable. > I'm still looking for a MS-Windows and a MacOSX buildbot host so that we > can automatically generate stellarium installers per commit. > If you think this is worthwhile to persue of course. Hi! In the moment I am working on a script that will allow CMake to generate the Inno Setup project file necessary for generating a Windows installer. :) I'm going to commit it later tonight. Bogdan |
From: <ha...@la...> - 2010-03-26 20:02:38
|
Bogdan Marinov wrote on 20100326: > On Fri, Mar 26, 2010 at 9:44 PM, H <ha...@la...> wrote: > > -just breaking in on this thread- > > > > Bogdan Marinov wrote on 20100326: > > ... > >> computer is not very > >> suitable for a release. Compilation, especially on Windows, is > >> painfully slow, and I haven't tried to create an installer for some > >> time. > > > > This process is scriptable. > > I'm still looking for a MS-Windows and a MacOSX buildbot host so that we > > can automatically generate stellarium installers per commit. > > If you think this is worthwhile to persue of course. > > Hi! > > In the moment I am working on a script that will allow CMake to > generate the Inno Setup project file necessary for generating a > Windows installer. :) I'm going to commit it later tonight. Ah, good. I have no experience with Inno Setup (had never heard of it until now). I've briefly perused http://www.jrsoftware.org/ but could not find if one can script it the installer generation. I do have some experience with scripting the NSIS installer from perl. -- Hans |
From: Bogdan M. <dag...@gm...> - 2010-03-26 20:40:59
|
On Fri, Mar 26, 2010 at 10:02 PM, H <ha...@la...> wrote: > Ah, good. I have no experience with Inno Setup (had never heard of it > until now). I've briefly perused http://www.jrsoftware.org/ but could > not find if one can script it the installer generation. I do have some > experience with scripting the NSIS installer from perl. I've committed the changes: http://stellarium.svn.sourceforge.net/viewvc/stellarium?view=rev&revision=6052 Now the Inno Setup script file (stellarium.iss) is generated from stellarium.iss.cmake when CMake is run, in the same way config.h is generated from config.h.cmake. I've also changed the paths so all library files are taken from the respective directories without the need to copy them manually. :) Inno Setup can be run from the command line: http://www.jrsoftware.org/ishelp/topic_compilercmdline.htm (The documentation uses frames, the main page is http://www.jrsoftware.org/ishelp/ ) Bogdan |
From: Barry G. <bar...@ho...> - 2010-03-26 21:58:57
|
Hi Bogdan I tried your new *.iss file but it does not work for me without editing The default location of the stellarium.exe and libstelmain.dll, using Fabiens original instructions is \prog\stellarium\qtcreator-build\src\stellarium.exe \prog\stellarium\qtcreator-build\src\libstelmain.dll I have never worked out how to automatically generate the share, locale sub directories so I have always created them manually. I use \prog\share\* \prog\locale\* and update them manually after each new build. Similarly I have never found out how to generate the locale diretory contents from the Gmo files. I don't know how this was done originally but I just use a DOS batch file that I painstakingly wrote Other than this it works OK Barry Gerdes Beaumont Hills Observatory S 33' 41' 44" E 150' 56' 32" > Date: Fri, 26 Mar 2010 22:40:51 +0200 > From: dag...@gm... > To: ste...@li... > Subject: Re: [Stellarium-pubdevel] Linking error in dynamic plug-ins with a GUI on Windows > > On Fri, Mar 26, 2010 at 10:02 PM, H <ha...@la...> wrote: > > Ah, good. I have no experience with Inno Setup (had never heard of it > > until now). I've briefly perused http://www.jrsoftware.org/ but could > > not find if one can script it the installer generation. I do have some > > experience with scripting the NSIS installer from perl. > > I've committed the changes: > http://stellarium.svn.sourceforge.net/viewvc/stellarium?view=rev&revision=6052 > > Now the Inno Setup script file (stellarium.iss) is generated from > stellarium.iss.cmake when CMake is run, in the same way config.h is > generated from config.h.cmake. I've also changed the paths so all > library files are taken from the respective directories without the > need to copy them manually. :) > > Inno Setup can be run from the command line: > http://www.jrsoftware.org/ishelp/topic_compilercmdline.htm > (The documentation uses frames, the main page is > http://www.jrsoftware.org/ishelp/ ) > > Bogdan > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel _________________________________________________________________ Browse profiles for FREE! Meet local singles online. http://clk.atdmt.com/NMN/go/150855801/direct/01/ |
From: Fabien C. <fab...@go...> - 2010-03-26 22:23:46
|
Barry to generate the things you mention, just type "make package". Fabien On Fri, Mar 26, 2010 at 22:58, Barry Gerdes <bar...@ho...> wrote: > Hi Bogdan > > I tried your new *.iss file but it does not work for me without editing > The default location of the stellarium.exe and libstelmain.dll, using > Fabiens original instructions is > \prog\stellarium\qtcreator-build\src\stellarium.exe > \prog\stellarium\qtcreator-build\src\libstelmain.dll > > I have never worked out how to automatically generate the share, locale sub > directories so I have always created them manually. I use > \prog\share\* > \prog\locale\* > and update them manually after each new build. > > Similarly I have never found out how to generate the locale diretory > contents from the Gmo files. I don't know how this was done originally but I > just use a DOS batch file that I painstakingly wrote > > Other than this it works OK > > Barry Gerdes > Beaumont Hills Observatory > S 33' 41' 44" E 150' 56' 32" > > > >> Date: Fri, 26 Mar 2010 22:40:51 +0200 >> From: dag...@gm... >> To: ste...@li... >> Subject: Re: [Stellarium-pubdevel] Linking error in dynamic plug-ins with >> a GUI on Windows >> >> On Fri, Mar 26, 2010 at 10:02 PM, H <ha...@la...> wrote: >> > Ah, good. I have no experience with Inno Setup (had never heard of it >> > until now). I've briefly perused http://www.jrsoftware.org/ but could >> > not find if one can script it the installer generation. I do have some >> > experience with scripting the NSIS installer from perl. >> >> I've committed the changes: >> >> http://stellarium.svn.sourceforge.net/viewvc/stellarium?view=rev&revision=6052 >> >> Now the Inno Setup script file (stellarium.iss) is generated from >> stellarium.iss.cmake when CMake is run, in the same way config.h is >> generated from config.h.cmake. I've also changed the paths so all >> library files are taken from the respective directories without the >> need to copy them manually. :) >> >> Inno Setup can be run from the command line: >> http://www.jrsoftware.org/ishelp/topic_compilercmdline.htm >> (The documentation uses frames, the main page is >> http://www.jrsoftware.org/ishelp/ ) >> >> Bogdan >> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Stellarium-pubdevel mailing list >> Ste...@li... >> https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > > ________________________________ > Meet local singles online. Browse profiles for FREE! > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > > |
From: Barry G. <bar...@ho...> - 2010-03-26 22:48:18
|
Hi Fabien Yes I just worked that out I did a linux compile and "Make install" That fixed my linux Then a make install under "msys" That did the same for Windows So I went searching for a way to do it under Qtcreator. Now I know how it is done I can revert to my own method that suits me better Incidently I started a build all under Qtcreator for Windows and while it was working I switched on my linux computer. Updated the src to 6052 then did the cmake ../.. followed by a make then a sudo make install. I had the Linux version up and running while the Windows compile was still only half done. Barry Gerdes Beaumont Hills Observatory S 33' 41' 44" E 150' 56' 32" > From: fab...@go... > Date: Fri, 26 Mar 2010 23:23:19 +0100 > To: ste...@li... > Subject: Re: [Stellarium-pubdevel] Linking error in dynamic plug-ins with a GUI on Windows > > Barry to generate the things you mention, just type "make package". > Fabien > > On Fri, Mar 26, 2010 at 22:58, Barry Gerdes <bar...@ho...> wrote: > > Hi Bogdan > > > > I tried your new *.iss file but it does not work for me without editing > > The default location of the stellarium.exe and libstelmain.dll, using > > Fabiens original instructions is > > \prog\stellarium\qtcreator-build\src\stellarium.exe > > \prog\stellarium\qtcreator-build\src\libstelmain.dll > > > > I have never worked out how to automatically generate the share, locale sub > > directories so I have always created them manually. I use > > \prog\share\* > > \prog\locale\* > > and update them manually after each new build. > > > > Similarly I have never found out how to generate the locale diretory > > contents from the Gmo files. I don't know how this was done originally but I > > just use a DOS batch file that I painstakingly wrote > > > > Other than this it works OK > > > > Barry Gerdes > > Beaumont Hills Observatory > > S 33' 41' 44" E 150' 56' 32" > > > > > > > >> Date: Fri, 26 Mar 2010 22:40:51 +0200 > >> From: dag...@gm... > >> To: ste...@li... > >> Subject: Re: [Stellarium-pubdevel] Linking error in dynamic plug-ins with > >> a GUI on Windows > >> > >> On Fri, Mar 26, 2010 at 10:02 PM, H <ha...@la...> wrote: > >> > Ah, good. I have no experience with Inno Setup (had never heard of it > >> > until now). I've briefly perused http://www.jrsoftware.org/ but could > >> > not find if one can script it the installer generation. I do have some > >> > experience with scripting the NSIS installer from perl. > >> > >> I've committed the changes: > >> > >> http://stellarium.svn.sourceforge.net/viewvc/stellarium?view=rev&revision=6052 > >> > >> Now the Inno Setup script file (stellarium.iss) is generated from > >> stellarium.iss.cmake when CMake is run, in the same way config.h is > >> generated from config.h.cmake. I've also changed the paths so all > >> library files are taken from the respective directories without the > >> need to copy them manually. :) > >> > >> Inno Setup can be run from the command line: > >> http://www.jrsoftware.org/ishelp/topic_compilercmdline.htm > >> (The documentation uses frames, the main page is > >> http://www.jrsoftware.org/ishelp/ ) > >> > >> Bogdan > >> > >> > >> ------------------------------------------------------------------------------ > >> Download Intel® Parallel Studio Eval > >> Try the new software tools for yourself. Speed compiling, find bugs > >> proactively, and fine-tune applications for parallel performance. > >> See why Intel Parallel Studio got high marks during beta. > >> http://p.sf.net/sfu/intel-sw-dev > >> _______________________________________________ > >> Stellarium-pubdevel mailing list > >> Ste...@li... > >> https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > > > > ________________________________ > > Meet local singles online. Browse profiles for FREE! > > ------------------------------------------------------------------------------ > > Download Intel® Parallel Studio Eval > > Try the new software tools for yourself. Speed compiling, find bugs > > proactively, and fine-tune applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > _______________________________________________ > > Stellarium-pubdevel mailing list > > Ste...@li... > > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > > > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel _________________________________________________________________ Link all your email accounts and social updates with Hotmail. Find out now. http://windowslive.ninemsn.com.au/oneinbox?ocid=T162MSN05A0710G |
From: Bogdan M. <dag...@gm...> - 2010-03-25 14:30:16
|
On Thu, Mar 25, 2010 at 3:26 PM, Fabien Chéreau <fab...@go...> wrote: > Ah now I know! There was the same problem in win32 before which is the > reason I had to create the libStelMain.dll instead of linking > everything in stellarium.exe > Now in the last release I made the GUI a static library linked with > stellarium.exe and forgot to code the case where GENERATE_STELMAINLIB > is defined. In this case the GUI code sjould be linked in > libsteMain.dll instead. Any preferences in which file to add the code? I'm using StelApp.cpp for now. Also, the Telescope class in the Oculars plug-in clashes with the Telescope class in Stellarium's main code. It may be a good idea to require namespaces in plug-ins. > Thanks Bogdan, I let you trying to deal with that (I don't have my > windows machine at the moment). Let me know if you find a way to fix > that. I hope I do. Bogdan. |
From: Fabien C. <fab...@go...> - 2010-03-25 16:41:39
|
On Thu, Mar 25, 2010 at 15:30, Bogdan Marinov <dag...@gm...> wrote: > On Thu, Mar 25, 2010 at 3:26 PM, Fabien Chéreau > <fab...@go...> wrote: >> Ah now I know! There was the same problem in win32 before which is the >> reason I had to create the libStelMain.dll instead of linking >> everything in stellarium.exe >> Now in the last release I made the GUI a static library linked with >> stellarium.exe and forgot to code the case where GENERATE_STELMAINLIB >> is defined. In this case the GUI code sjould be linked in >> libsteMain.dll instead. > > Any preferences in which file to add the code? I'm using StelApp.cpp for now. Normally you only have to modify the src/CMakeList.txt, no code change are required. > Also, the Telescope class in the Oculars plug-in clashes with the > Telescope class in Stellarium's main code. It may be a good idea to > require namespaces in plug-ins. Actually, are the Telescope and TelescopeMgr classes still required in Stellarium or are they deprecated by your plugin? If they are deprecated please suppress them! |
From: Bogdan M. <dag...@gm...> - 2010-03-25 20:47:31
Attachments:
plugins_linking_fix.diff
|
On Thu, Mar 25, 2010 at 6:41 PM, Fabien Chéreau <fab...@go...> wrote: > Normally you only have to modify the src/CMakeList.txt, no code change > are required. I don't think so. At the moment, static plug-ins are imported in main.cpp, which is in stellarium_exe_SRCS (the list of source files used to compile the executable), not in stellarium_lib_SRCS (where is StelApp.cpp). See the attached patch for my proposed solution. It seems to work, except for the issue with the Oculars plug-in. I wonder why there's no conflict on Linux... > Actually, are the Telescope and TelescopeMgr classes still required in > Stellarium or are they deprecated by your plugin? > If they are deprecated please suppress them! Not exactly. The module is active when my plug-in is not loaded. It can be used if for some reason using a GUI is not desirable. Any preferred way to deal with the conflict? Anyway, the attached patch seems to work - I've managed to build and load the ExampleDialog plug-in. Everything seems to be OK except for a small compile-time issue with libintl.h. Bogdan |
From: Fabien C. <fab...@go...> - 2010-03-26 09:44:38
|
OK thanks Bogdan! I applied a modified version of your patch (r 6047), I just moved everything from main.cpp to StelApp.cpp instead of duplicating the code. Tell me if it works. Fabien On Thu, Mar 25, 2010 at 21:47, Bogdan Marinov <dag...@gm...> wrote: > On Thu, Mar 25, 2010 at 6:41 PM, Fabien Chéreau > <fab...@go...> wrote: >> Normally you only have to modify the src/CMakeList.txt, no code change >> are required. > > I don't think so. At the moment, static plug-ins are imported in > main.cpp, which is in stellarium_exe_SRCS (the list of source files > used to compile the executable), not in stellarium_lib_SRCS (where is > StelApp.cpp). See the attached patch for my proposed solution. It > seems to work, except for the issue with the Oculars plug-in. I wonder > why there's no conflict on Linux... > >> Actually, are the Telescope and TelescopeMgr classes still required in >> Stellarium or are they deprecated by your plugin? >> If they are deprecated please suppress them! > > Not exactly. The module is active when my plug-in is not loaded. It > can be used if for some reason using a GUI is not desirable. > > Any preferred way to deal with the conflict? > > Anyway, the attached patch seems to work - I've managed to build and > load the ExampleDialog plug-in. Everything seems to be OK except for a > small compile-time issue with libintl.h. > > Bogdan > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > > |
From: Bogdan M. <dag...@gm...> - 2010-03-26 12:31:12
|
On Fri, Mar 26, 2010 at 11:44 AM, Fabien Chéreau <fab...@go...> wrote: > OK thanks Bogdan! > I applied a modified version of your patch (r 6047), I just moved > everything from main.cpp to StelApp.cpp instead of duplicating the > code. > Tell me if it works. Yes, after fixing the conflict with the Oculars plug-in (revision 6050) everything is OK - the external plug-ins are built and loaded without a problem. I've tested it in Windows and in Linux. Bogdan |
From: Fabien C. <fab...@go...> - 2010-03-26 14:36:07
|
Nice :) By the way Bogdan, if you wish and have time for that you can try to organize/create the release yourself. Currently it was always me or Matthew, but we are quite busy in the next weeks. And it's always good for the project that some new people do that :) Fabien On Fri, Mar 26, 2010 at 13:30, Bogdan Marinov <dag...@gm...> wrote: > On Fri, Mar 26, 2010 at 11:44 AM, Fabien Chéreau > <fab...@go...> wrote: >> OK thanks Bogdan! >> I applied a modified version of your patch (r 6047), I just moved >> everything from main.cpp to StelApp.cpp instead of duplicating the >> code. >> Tell me if it works. > > Yes, after fixing the conflict with the Oculars plug-in (revision > 6050) everything is OK - the external plug-ins are built and loaded > without a problem. I've tested it in Windows and in Linux. > > Bogdan > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > |
From: Barry G. <bar...@ho...> - 2010-03-26 20:26:17
|
Hi Fabien I create a Windows installer every time I build, usually every morning if there have been code changes in the source. This enables me to quickly check out the build on all my computers. I can probably load it onto iceinspace temporarily while someone collects it. Just tell me how you want it configured because my builds have all options compiled. Barry Gerdes Beaumont Hills Observatory S 33' 41' 44" E 150' 56' 32" > From: fab...@go... > Date: Fri, 26 Mar 2010 15:35:40 +0100 > To: ste...@li... > Subject: Re: [Stellarium-pubdevel] Linking error in dynamic plug-ins with a GUI on Windows > > Nice :) > By the way Bogdan, if you wish and have time for that you can try to > organize/create the release yourself. Currently it was always me or > Matthew, but we are quite busy in the next weeks. And it's always good > for the project that some new people do that :) > Fabien > > On Fri, Mar 26, 2010 at 13:30, Bogdan Marinov <dag...@gm...> wrote: > > On Fri, Mar 26, 2010 at 11:44 AM, Fabien Chéreau > > <fab...@go...> wrote: > >> OK thanks Bogdan! > >> I applied a modified version of your patch (r 6047), I just moved > >> everything from main.cpp to StelApp.cpp instead of duplicating the > >> code. > >> Tell me if it works. > > > > Yes, after fixing the conflict with the Oculars plug-in (revision > > 6050) everything is OK - the external plug-ins are built and loaded > > without a problem. I've tested it in Windows and in Linux. > > > > Bogdan > > > > ------------------------------------------------------------------------------ > > Download Intel® Parallel Studio Eval > > Try the new software tools for yourself. Speed compiling, find bugs > > proactively, and fine-tune applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > _______________________________________________ > > Stellarium-pubdevel mailing list > > Ste...@li... > > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel _________________________________________________________________ Get the latest jobs delivered. Sign up for SEEK Jobmail. http://clk.atdmt.com/NMN/go/157639755/direct/01/ |