Hi!
Thanks for checkout build in Linux.
Cheers!
2014-03-18 9:39 GMT+01:00 Konstantin Dmitriev :
> Hi!
>
> Thank you for the fixes!
> I have tested your master branch on Linux - haven't noticed any problems
> here.
> We are still investigating the Win32 build issues. No luck yet, but
> we'll keep
Hi!
Thank you for the fixes!
I have tested your master branch on Linux - haven't noticed any problems here.
We are still investigating the Win32 build issues. No luck yet, but
we'll keep digging. ^__^
Regards,
K.
2014-03-18 14:12 GMT+07:00 Carlos López González :
> OK. I've been researching tha
OK. I've been researching that combination of gnu extension symbol not
found and everything points to the default usage of the new libc++ as
replacement of the libstdc++ in OSX 10.9.x
I've not found a way to fix this from the root cause so I decided to
disable the line for the OSX platform. See:
Right. I am building packages with DEBUG=0, that's why I haven't
noticed it before.
K.
2014-03-11 0:57 GMT+07:00 Carlos López González :
> Confirmed. Running:
> $ sudo sh synfigstudio-osx-build.sh
> produces in debug mode (export DEBUG=1 at line 65 of the script) the
> following error:
>
> main.c
Confirmed. Running:
$ sudo sh synfigstudio-osx-build.sh
produces in debug mode (export DEBUG=1 at line 65 of the script) the
following error:
main.cpp:196:21: error: use of undeclared identifier '__gnu_cxx'
std::set_terminate(__gnu_cxx::__verbose_terminate_handler);
Hi!
I don't have OSX on hand right now, but IIRC the synfigstudio binary
is placed to ~/src/macports/SynfigStudio-app/Contents/Resources/bin/
You can start it from terminal, but the best way is to run
~/src/macports/SynfigStudio-app/Contents/MacOS/SynfigStudio
Regards,
K.
2014-03-10 14:38 GMT+0
One question:
2014-03-09 12:00 GMT+01:00 Konstantin Dmitriev :
> Hello!
>
> FYI, the autobuild script doesn't use libstdc++ compilation.
> Why won't you use autobuild script in the same way ad you do for windows?
> ^__^
>
After use the script, where is placed the synfigstudio executable? And
also
El domingo, 9 de marzo de 2014, Konstantin Dmitriev
escribió:
> Hello!
>
> FYI, the autobuild script doesn't use libstdc++ compilation.
Then the script should raise the same error. I think I've not noticed it
before because I've not run the script in debug mode.
> Why won't you use autobuild sc
Hello!
FYI, the autobuild script doesn't use libstdc++ compilation.
Why won't you use autobuild script in the same way ad you do for windows? ^__^
(BTW, it would be nice to mention, which exact main.cpp file produces tis error)
Regards,
K.
2014-03-09 15:22 GMT+07:00 Carlos López González :
> H
Hi! Unfortunately only the autobuild scripts works with this new Mavericks.
I have not been able to build Synfig using native compiler (aka clang) and
Macports.
It raises an error that I've not been able to fix yet.
If someone want to reproduce it, this is the recipe:
1) Macports needs to be updat
I'm glad to know you got that fixed!
K.
"Carlos López González" пишет:
>Hi!
>Finally I was able to update my Macports so I can run the build
>scripts. A
>lot of warnings and some errors are raised from the new compiler of OSX
>10.9 so I'm trying to fix them.
>
>Once I have them finished I'll send
Hi!
Finally I was able to update my Macports so I can run the build scripts. A
lot of warnings and some errors are raised from the new compiler of OSX
10.9 so I'm trying to fix them.
Once I have them finished I'll send a pull request.
Cheers!
--
Carlos
http://synfig.org
-
12 matches
Mail list logo
