From: Johannes R. <por...@ya...> - 2013-02-07 20:04:54
|
Hi, I have been trying out the gsoc2009-matevz branch for some of my tests using c++11 features... I got it to compile using the MinGW as directed in the swig documentation However, the executable I get seems to require libstdc++-6.dll. With that everything seems to work fine, but I would like to have it statically linked to the executable... For some reason just adding this -static-libstdc++ to the linker options does not seem to suffice. Any thoughts how I could make it work? Thanks! |
From: William S F. <ws...@fu...> - 2013-02-08 06:55:24
|
On 07/02/13 20:04, Johannes Rajala wrote: > Hi, > I have been trying out the gsoc2009-matevz branch for some of my tests using c++11 features... > > I got it to compile using the MinGW as directed in the swig documentation However, the executable I get seems to require libstdc++-6.dll. With that everything seems to work fine, but I would like to have it statically linked to the executable... For some reason just adding this -static-libstdc++ to the linker options does not seem to suffice. > > Any thoughts how I could make it work? Are you talking about swig.exe rather than your own executable? Running './autogen.sh && ./configure && make' should just work without requiring the dll you mention. I'd expect that this branch doesn't work any differently to trunk. But in case, you might want to check your environment by building trunk or say swig-2.0.9. If you have any feedback on the C++11 support let me know, it is now very close to being put into a release. William |
From: Johannes R. <por...@ya...> - 2013-02-11 10:27:25
|
> On 07/02/13 20:04, Johannes Rajala wrote: >> Hi, >> I have been trying out the gsoc2009-matevz branch for some of my tests > using c++11 features... >> >> I got it to compile using the MinGW as directed in the swig documentation > However, the executable I get seems to require libstdc++-6.dll. With that > everything seems to work fine, but I would like to have it statically linked to > the executable... For some reason just adding this -static-libstdc++ to the > linker options does not seem to suffice. >> >> Any thoughts how I could make it work? > > Are you talking about swig.exe rather than your own executable? Running > './autogen.sh && ./configure && make' should just work > without requiring the dll you mention. I'd expect that this branch > doesn't work any differently to trunk. But in case, you might want to check > your environment by building trunk or say swig-2.0.9. > > If you have any feedback on the C++11 support let me know, it is now very close > to being put into a release. > > William > Thanks, yes - I was speaking of the swig.exe that I created from the sources and then tried to run in order to create lua bindings. Now, I got the original 2.0.9 and did the autogen,configure,make and it seems to be doing the same thing when I build it myself (need the dll). Also the executable I create is 5.8MB while the original is 1.7MB. The MinGW I have(mingw-get-inst-20120426) did install a bit differently from the instructions: As I run the installer I chose the c, c++ and DTK, then installed the rest by hand (mingw-get install <autoconf, automake, bison>). So, I am not sure if there was something different. So, in the end it does not seem to be related to the c++11 branch. With the dll's, everything seems to work there on Windows. |
From: Johannes R. <por...@ya...> - 2013-02-11 12:18:20
|
>> On 07/02/13 20:04, Johannes Rajala wrote: > >>> Hi, >>> I have been trying out the gsoc2009-matevz branch for some of my tests > >> using c++11 features... >>> >>> I got it to compile using the MinGW as directed in the swig > documentation >> However, the executable I get seems to require libstdc++-6.dll. With that >> everything seems to work fine, but I would like to have it statically > linked to >> the executable... For some reason just adding this -static-libstdc++ to the > >> linker options does not seem to suffice. >>> >>> Any thoughts how I could make it work? >> >> Are you talking about swig.exe rather than your own executable? Running >> './autogen.sh && ./configure && make' should just > work >> without requiring the dll you mention. I'd expect that this branch >> doesn't work any differently to trunk. But in case, you might want to > check >> your environment by building trunk or say swig-2.0.9. >> >> If you have any feedback on the C++11 support let me know, it is now very > close >> to being put into a release. >> >> William >> > > Thanks, > yes - I was speaking of the swig.exe that I created from the sources and then > tried to run in order to create lua bindings. > > Now, I got the original 2.0.9 and did the autogen,configure,make and it seems to > be doing the same thing when I build it myself (need the dll). Also the > executable I create is 5.8MB while the original is 1.7MB. > > The MinGW I have(mingw-get-inst-20120426) did install a bit differently from the > instructions: As I run the installer I chose the c, c++ and DTK, then installed > the rest by hand (mingw-get install <autoconf, automake, bison>). So, I am > not sure if there was something different. > > So, in the end it does not seem to be related to the c++11 branch. With the > dll's, everything seems to work there on Windows. > Just re-did the MinGW installation: 1. installed: mingw-get-inst-20120426.exe Select: c, c++, DTK 2. (just in case) run the: C:\MinGW\msys\1.0\postinstall\pi.bat 3. Run MinGW Shell cd /usr mkdir src cd src git clone https://github.com/swig/swig.git (yes, just trying now with the 'master') cd swig ./autogen.sh 4. Downloaded the pcre-8.32.tar.bz2 to swig folder 5. back to the MinGW Shell cd /usr/src/swig Tools/pcre-build.sh ./configure make Now when I copy the generated executable to my project and try this kind of command: swig.exe -Wextra -w302,325,403,504,509,512,302 -lua -c++ -I../include -o test.cpp ../include/luainterface.i I get the following error message: "The Program can't start because libstdc++-6.dll is missing from your computer." ...so the same issue still exists, here is just more detailed steps to reproduce. /Johannes |
From: Johannes R. <por...@ya...> - 2013-02-12 13:27:56
|
>> On 07/02/13 20:04, Johannes Rajala wrote: > >>> Hi, >>> I have been trying out the gsoc2009-matevz branch for some of my tests > >> using c++11 features... >>> >>> I got it to compile using the MinGW as directed in the swig > documentation >> However, the executable I get seems to require libstdc++-6.dll. With that >> everything seems to work fine, but I would like to have it statically > linked to >> the executable... For some reason just adding this -static-libstdc++ to the > >> linker options does not seem to suffice. >>> >>> Any thoughts how I could make it work? >> >> Are you talking about swig.exe rather than your own executable? Running >> './autogen.sh && ./configure && make' should just > work >> without requiring the dll you mention. I'd expect that this branch >> doesn't work any differently to trunk. But in case, you might want to > check >> your environment by building trunk or say swig-2.0.9. >> >> If you have any feedback on the C++11 support let me know, it is now very > close >> to being put into a release. >> >> William >> > > Thanks, > yes - I was speaking of the swig.exe that I created from the sources and then > tried to run in order to create lua bindings. > > Now, I got the original 2.0.9 and did the autogen,configure,make and it seems to > be doing the same thing when I build it myself (need the dll). Also the > executable I create is 5.8MB while the original is 1.7MB. > > The MinGW I have(mingw-get-inst-20120426) did install a bit differently from the > instructions: As I run the installer I chose the c, c++ and DTK, then installed > the rest by hand (mingw-get install <autoconf, automake, bison>). So, I am > not sure if there was something different. > > So, in the end it does not seem to be related to the c++11 branch. With the > dll's, everything seems to work there on Windows. > On another note... (this is specific to the c++11 branch): I am trying to create a swig build on OS X, and it gives this kind of error: configure: creating ./config.status config.status: creating Makefile config.status: creating config.h CParse/.deps/cscanner.Po:1: *** multiple target patterns. Stop. make: *** [source] Error 2 ... Installing /.../swig-osx/share/man/man1/ccache-swig.1 install: ./ccache-swig.1: No such file or directory make[1]: *** [install] Error 71 make: *** [install-ccache] Error 2 ...I guess this should work on OS X as well? Thanks again... |
From: William S F. <ws...@fu...> - 2013-02-28 07:01:46
|
On 12/02/13 13:27, Johannes Rajala wrote: > > On another note... (this is specific to the c++11 branch): > > I am trying to create a swig build on OS X, and it gives this kind of error: > configure: creating ./config.status > > config.status: creating Makefile > config.status: creating config.h > CParse/.deps/cscanner.Po:1: *** multiple target patterns. Stop. > make: *** [source] Error 2 > ... You should see ccache-swig.1 being built if it doesn't exist at this point in the log. > Installing /.../swig-osx/share/man/man1/ccache-swig.1 > install: ./ccache-swig.1: No such file or directory > make[1]: *** [install] Error 71 > make: *** [install-ccache] Error 2 > > ...I guess this should work on OS X as well? Yes and it shouldn't be any different to master. William |
From: Johannes R. <por...@ya...> - 2013-08-22 12:22:34
|
Hi... when do you plan to merge the c++11 branch to the master (and eventually release it)? Thanks |
From: William S F. <ws...@fu...> - 2013-08-29 05:59:32
|
On 22/08/13 13:22, Johannes Rajala wrote: > Hi... > when do you plan to merge the c++11 branch to the master (and eventually release it)? > See my email just posted about SWIG 3. William |