cyrille henry wrote: > > > compiing look good in the beginning, but stop on the 1st pix object : > make -C Pixes make[1]: entrant dans le répertoire « > /home/nusmuk/pd/Gem/src/Pixes » > In file included from /usr/include/avifile-0.7/avm_stl.h:7, > from /usr/include/avifile-0.7/avifile.h:4, > from ../Pixes/filmAVIPLAY.h:31, > from pix_film.cpp:27: > /usr/include/avifile-0.7/avm_default.h:7:56: error: config.h: Aucun > fichier ou dossier de ce type > > ./configure --without-avifile allow me to finish compilling. > but avi use to work...
hmm, i suspect this to be a bug in avifile: autoconf will define HAVE_CONFIG_H when it generates a config.h-file (regardless of it's name); e.g. if our config.h file is actually called MySuperConfig.h, autoconf will still define HAVE_CONFIG_H. now, when we include /usr/include/avifile-0.7/avifile.h with HAVE_CONFIG_H defined, it will try to include a file called "config.h", which might not exist (because HAVE_CONFIG_H only tells us that we have MySuperConfig.h), and thus compilation will fail. i personally don't think that a public header-file should include any-file based on HAVE_CONFIG_H. but then, i couldn't find any reference to prove my suspection. anyhow, for now i have undefined HAVE_CONFIG_H in GemConfig.h after it has included the generated config.h, which should fix the problem with avifile. please try whether it works fgmasdr IOhannes
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ GEM-dev mailing list [email protected] http://lists.puredata.info/listinfo/gem-dev
