-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
ola,
some of you might have noticed that in the last few days, i have worked a bit on the Gem autotools based build system.
this most likely means, that Gem won't compile anymore if you just do an "svn update" and do as you are used to.
the good thing is, that the autotools build system is now (almost) complete, with handcruft slowly fading out.
what you have to take into account (aka major changes):
- - the root of the build system is no longer .../Gem/src but .../Gem/
in order to build Gem from a fresh checkout you now do ~$ cd .../Gem .../Gem$ ./autogen.sh .../Gem$ ./configure .../Gem$ make .../Gem$ make install
which should (by default) install everything into /usr/local/lib/pd/extra (Gem + plugins + help-patches+manuals will be installed into pd/extra/Gem/ and extras will be installed as (e.g.) /usr/local/lib/pd/extra/pix_drum/
- - there are some compat scripts (.../Gem/src/autogen.sh and .../Gem/src/configure) to ease transition (esp. for the autobuild system)
these scripts basically only call their equivalents in .../Gem and pass all arguments.
these dummy scripts will most likely generate an error when doing an "svn update" in an already configured tree as it will want to overwrite the (old auto-generated) ...Gem/src/configure; simply delete the generated configure script and rerun "svn update" to get the new stub.
i hope that having the build-system properly working (again) helps for the next release.
fgamr IOhannes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-30 09:47, IOhannes m zmoelnig wrote:
what you have to take into account (aka major changes):
- the root of the build system is no longer .../Gem/src but .../Gem/
first thing i forgot: any convenience links (to not have to search for "Gem.pd_linux" in some obscure .libs/ directory) will be created into .../Gem/ as well.
fgmasdr IOhannes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-30 10:17, IOhannes m zmoelnig wrote:
On 2011-06-30 09:47, IOhannes m zmoelnig wrote:
what you have to take into account (aka major changes):
- the root of the build system is no longer .../Gem/src but .../Gem/
first thing i forgot: any convenience links (to not have to search for "Gem.pd_linux" in some obscure .libs/ directory) will be created into .../Gem/ as well.
2nd thing: config.h is now generated in .../Gem/src you might want to remove your .../Gem/src/Base/config.h manually, in order to avoid inclusion of the wrong config.h
fgamsdr IOhannes
On Jun 30, 2011, at 12:15 PM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-30 10:17, IOhannes m zmoelnig wrote:
On 2011-06-30 09:47, IOhannes m zmoelnig wrote:
what you have to take into account (aka major changes):
- the root of the build system is no longer .../Gem/src but .../Gem/
first thing i forgot: any convenience links (to not have to search for "Gem.pd_linux" in some obscure .libs/ directory) will be created into .../Gem/ as well.
2nd thing: config.h is now generated in .../Gem/src you might want to remove your .../Gem/src/Base/config.h manually, in order to avoid inclusion of the wrong config.h
That sounds like something the build system should do. If an included header is out of date, the build system should update it.
.hc
----------------------------------------------------------------------------
I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone." --Bjarne Stroustrup (creator of C++)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-30 18:23, Hans-Christoph Steiner wrote:
That sounds like something the build system should do. If an included header is out of date, the build system should update it.
i'm talking about leftovers from the older build system.
both the olde and the new build system will handle the config.h quite well and automatically. but if you change the build-system in a non-clean state (e.g. because you do an "svn update" after having run ./autogen.sh), then it gets confused.
fgmar IOhannes
On Jun 30, 2011, at 12:30 PM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-30 18:23, Hans-Christoph Steiner wrote:
That sounds like something the build system should do. If an included header is out of date, the build system should update it.
i'm talking about leftovers from the older build system.
both the olde and the new build system will handle the config.h quite well and automatically. but if you change the build-system in a non-clean state (e.g. because you do an "svn update" after having run ./autogen.sh), then it gets confused.
pd@debian-lenny-i386 ~ $ cd /home/pd/rsync/pd-extended/externals/Gem pd@debian-lenny-i386 Gem $ svn st pd@debian-lenny-i386 Gem $ find . -name config.h pd@debian-lenny-i386 Gem $
There is no config.h there. Each auto-build starts with an rsync which deletes any file that isn't in /home/pd/rsync, so that's the same for all of the builds.
.hc
----------------------------------------------------------------------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-30 19:19, Hans-Christoph Steiner wrote:
pd@debian-lenny-i386 ~ $ cd /home/pd/rsync/pd-extended/externals/Gem pd@debian-lenny-i386 Gem $ svn st pd@debian-lenny-i386 Gem $ find . -name config.h pd@debian-lenny-i386 Gem $
There is no config.h there. Each auto-build starts with an rsync which deletes any file that isn't in /home/pd/rsync, so that's the same for all of the builds.
sure, i never doubted that. however, there are people out there, who do compile Gem themselves, and who do not start with a fresh checkout everytime.
mfgasdr IOhannes
Hello Iohannes,
cool, here it compiles very easily (osx 10.6 / 0.42.5), pix_film, pix_video are working with the Darwin.so plugin text2d is rendered (using libftgl2 from fink) but pix_image crashes pd, this happens with the QT plugin as I have no gem_imageDarwin. if you want more info i can test with gdb when i have more time.
thx for your work best
nicolas
Le 30/06/11 09:47, IOhannes m zmoelnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
ola,
some of you might have noticed that in the last few days, i have worked a bit on the Gem autotools based build system.
this most likely means, that Gem won't compile anymore if you just do an "svn update" and do as you are used to.
the good thing is, that the autotools build system is now (almost) complete, with handcruft slowly fading out.
what you have to take into account (aka major changes):
- the root of the build system is no longer .../Gem/src but .../Gem/
in order to build Gem from a fresh checkout you now do ~$ cd .../Gem .../Gem$ ./autogen.sh .../Gem$ ./configure .../Gem$ make .../Gem$ make install
which should (by default) install everything into /usr/local/lib/pd/extra (Gem + plugins + help-patches+manuals will be installed into pd/extra/Gem/ and extras will be installed as (e.g.) /usr/local/lib/pd/extra/pix_drum/
- there are some compat scripts (.../Gem/src/autogen.sh and
.../Gem/src/configure) to ease transition (esp. for the autobuild system)
these scripts basically only call their equivalents in .../Gem and pass all arguments.
these dummy scripts will most likely generate an error when doing an "svn update" in an already configured tree as it will want to overwrite the (old auto-generated) ...Gem/src/configure; simply delete the generated configure script and rerun "svn update" to get the new stub.
i hope that having the build-system properly working (again) helps for the next release.
fgamr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4MKhcACgkQkX2Xpv6ydvShEQCfdUhH9b9ISvxJ8euQVnFB+VA7 EB4AniEkLQuRcHW9NdRoUT2dfLJNox2Y =ZUH3 -----END PGP SIGNATURE-----
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/01/2011 01:56 AM, Nicolas Montgermont wrote:
but pix_image crashes pd, this happens with the QT plugin as I have no gem_imageDarwin.
yes, there is none.
if you want more info i can test with gdb when i have more time.
yes please.
however, i will leave for a 1 week holiday tomorrow, so i might not be able to do anything before july 10th
fgasmdr IOhannes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/01/2011 01:56 AM, Nicolas Montgermont wrote:
Hello Iohannes,
cool, here it compiles very easily (osx 10.6 / 0.42.5), pix_film, pix_video are working with the Darwin.so plugin text2d is rendered (using libftgl2 from fink) but pix_image crashes pd, this happens with the QT plugin as I have no gem_imageDarwin. if you want more info i can test with gdb when i have more time.
one more guess: could you try sending a [thread 0( message to [pix_image] before loading? afaik, QT is not thread save, and in theory the new image loading code should respect this, but maybe something went wrong.
and also try to run pd/Gem from the cmdline with "-stderr -verbose -verbose" and see what it gets you: $ /Applications/Pd.app/Contents/Resources/bin/pd -stderr -verbose - -verbose -lib /path/to/Gem/Gem masdrt IOhannes
Le 01/07/11 11:24, IOhannes m zmölnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
one more guess: could you try sending a [thread 0( message to [pix_image] before loading?
it crashes also
afaik, QT is not thread save, and in theory the new image loading code should respect this, but maybe something went wrong.
and also try to run pd/Gem from the cmdline with "-stderr -verbose -verbose" and see what it gets you: $ /Applications/Pd.app/Contents/Resources/bin/pd -stderr -verbose
- -verbose -lib /path/to/Gem/Gem
sure here it is: sending nothing to pix_image before loading a file:
load plugins 'image' in '' pattern : /Applications/Pd-extended-test.app/Contents/Resources/extra/Gem/gem_image*.so dylib loading file '/Applications/Pd-extended-test.app/Contents/Resources/extra/Gem/gem_imageQT.so'! tried /Applications/Pd-extended-test.app/Contents/Resources/extra/Gem/gem_imageQT.so and succeeded Image loading support: QT verbose( 1):threaded ImageLoading not supported! tried /Users/nix/Desktop/chdh.png and succeeded pure virtual method called begin blargh()unhandled exception end blargh()Pd: signal 6 closing audio... pure virtual method called begin blargh()unhandled exception end blargh()pd_gui: pd process exited
and sending thread 0 before: load plugins 'image' in '' pattern : /Applications/Pd-extended-test.app/Contents/Resources/extra/Gem/gem_image*.so dylib loading file '/Applications/Pd-extended-test.app/Contents/Resources/extra/Gem/gem_imageQT.so'! tried /Applications/Pd-extended-test.app/Contents/Resources/extra/Gem/gem_imageQT.so and succeeded Image loading support: QT verbose( 1):threaded ImageLoading not supported! tried /Users/nix/Desktop/chdh.png and succeeded pd_gui: pd process exited
good holidays :) n
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-07-01 20:23, Nicolas Montgermont wrote:
Image loading support: QT verbose( 1):threaded ImageLoading not supported! tried /Users/nix/Desktop/chdh.png and succeeded pd_gui: pd process exited
should work now (rev.4184)
good holidays :)
done.
famsdr IOhannes
great it's working! so I think i have everything now. tell me in the future if you need more testing on osx, i'll be glad to help. best,
n
Le 11/07/11 14:40, IOhannes m zmoelnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-07-01 20:23, Nicolas Montgermont wrote:
Image loading support: QT verbose( 1):threaded ImageLoading not supported! tried /Users/nix/Desktop/chdh.png and succeeded pd_gui: pd process exited
should work now (rev.4184)
-
Hans-Christoph Steiner -
IOhannes m zmoelnig -
IOhannes m zmölnig
-
Nicolas Montgermont