Hi
I don't know what the HAVE_CARBONQUICKTIME is all about, but it broke all of the QT code on the Mac because it does not actually enable any QT code at all! I am trying to build on 10.5, and obviously pix_film/video/record do nothing now. I guess this is in place in order to build on 10.6? What to do...
Chris
On 2010-04-02 00:46, chris clepper wrote:
Hi
I don't know what the HAVE_CARBONQUICKTIME is all about, but it broke all of the QT code on the Mac because it does not actually enable any QT code at all! I am trying to build on 10.5, and obviously pix_film/video/record do nothing now. I guess this is in place in order to build on 10.6? What to do...
define HAVE_CARBONQUICKTIME in the xcode project. the autobuilds don't use xcode but autoconf, which will define HAVE_CARBONQUICKTIME
and yes: HAVE_CARBONQUICKTIME was introduced for 10.6
fgmnasdr IOhannes
But all of the QT code is wrapped with HAVE_QUICKTIME, and in at least one case it looks like HAVE_CARBONQUICKTIME undefines HAVE_QUICKTIME.
Also, I tried the autoconf on 10.5 and it didn't get very far before dying.
On Tue, Apr 6, 2010 at 8:19 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
On 2010-04-02 00:46, chris clepper wrote:
Hi
I don't know what the HAVE_CARBONQUICKTIME is all about, but it broke all
of
the QT code on the Mac because it does not actually enable any QT code at all! I am trying to build on 10.5, and obviously pix_film/video/record
do
nothing now. I guess this is in place in order to build on 10.6? What
to
do...
define HAVE_CARBONQUICKTIME in the xcode project. the autobuilds don't use xcode but autoconf, which will define HAVE_CARBONQUICKTIME
and yes: HAVE_CARBONQUICKTIME was introduced for 10.6
fgmnasdr IOhannes
On 2010-04-06 14:57, chris clepper wrote:
But all of the QT code is wrapped with HAVE_QUICKTIME, and in at least one case it looks like HAVE_CARBONQUICKTIME undefines HAVE_QUICKTIME.
cannot reproduce. i checked all the files that make use of "HAVE_CARBONQUICKTIME" and have the "undef" keyword, which builds down to Pixes/filmQT.h Pixes/recordQT.h, and here HAVE_QUICKTIME get's undefined only if it's not w32 and HAVE_CARBONQT is not defined. so if HAVE_CARBONQUICKTIME is defined (which it has to be if carbon is available) it shouldn't make a difference.
Also, I tried the autoconf on 10.5 and it didn't get very far before dying.
that's weird; i compile Gem on 10.5 with autoconf quite often (and it's used with the autobuilds as well) and it works stable. my exact call to configure (including all the user-built statically libs) can be found here: http://gem.iem.at/documentation/faq/how-do-you-compile-gem-on-osx
(i usually don't use xcode, so that's why the project file is not being updated accordingly; sorry for that)
if you can post the error, i might be able to fix it.
fgamksdr IOhannes
On Tue, Apr 6, 2010 at 9:17 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
that's weird; i compile Gem on 10.5 with autoconf quite often (and it's used with the autobuilds as well) and it works stable. my exact call to configure (including all the user-built statically libs) can be found here: http://gem.iem.at/documentation/faq/how-do-you-compile-gem-on-osx
(i usually don't use xcode, so that's why the project file is not being updated accordingly; sorry for that)
if you can post the error, i might be able to fix it.
ACT-TECH01:src cgc$ autoconf ACT-TECH01:src cgc$ ./configure checking for g++... g++ checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes ./configure: line 2510: syntax error near unexpected token `PIC,' ./configure: line 2510: `GEM_ARG_ENABLE(PIC, PositionIndependentCode (potentially slower))'
On 2010-04-06 17:19, chris clepper wrote:
On Tue, Apr 6, 2010 at 9:17 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
that's weird; i compile Gem on 10.5 with autoconf quite often (and it's used with the autobuilds as well) and it works stable. my exact call to configure (including all the user-built statically libs) can be found here: http://gem.iem.at/documentation/faq/how-do-you-compile-gem-on-osx
(i usually don't use xcode, so that's why the project file is not being updated accordingly; sorry for that)
if you can post the error, i might be able to fix it.
ACT-TECH01:src cgc$ autoconf ACT-TECH01:src cgc$ ./configure checking for g++... g++ checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes ./configure: line 2510: syntax error near unexpected token `PIC,' ./configure: line 2510: `GEM_ARG_ENABLE(PIC, PositionIndependentCode (potentially slower))'
i see.
it should be:
% ./autogen.sh % ./configure % make
(you need to run aclocal before running autoconf; autogen.sh does this for you)
i have updated the documentation to reflect this change.
fgamsdr IOhannes
On Tue, Apr 6, 2010 at 9:17 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
On 2010-04-06 14:57, chris clepper wrote:
But all of the QT code is wrapped with HAVE_QUICKTIME, and in at least
one
case it looks like HAVE_CARBONQUICKTIME undefines HAVE_QUICKTIME.
cannot reproduce. i checked all the files that make use of "HAVE_CARBONQUICKTIME" and have the "undef" keyword, which builds down to Pixes/filmQT.h Pixes/recordQT.h, and here HAVE_QUICKTIME get's undefined only if it's not w32 and HAVE_CARBONQT is not defined. so if HAVE_CARBONQUICKTIME is defined (which it has to be if carbon is available) it shouldn't make a difference.
I defined both and the QT pix_ objects all did nothing when I compiled them. I had to change the undefine to define to get it going. Maybe there is something else in your setup or a mistake on my part?
The build setup on GEM has always been pretty bad, but now I have no idea what is what since it has been a long time since I set it up. The #ifdef hell has descended several more layers, and I think it is extremely difficult for even experienced developers to sort it out.
On Tue, Apr 6, 2010 at 9:17 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
(i usually don't use xcode, so that's why the project file is not being updated accordingly; sorry for that)
I don't blame you since XCode is kind of a disaster. It eats 3GB of RAM and two CPUs when I compile GEM - that's the IDE not the compiler!
On Tue, 6 Apr 2010, chris clepper wrote:
On Tue, Apr 6, 2010 at 9:17 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote: (i usually don't use xcode, so that's why the project file is not being updated accordingly; sorry for that)
I don't blame you since XCode is kind of a disaster. It eats 3GB of RAM and two CPUs when I compile GEM - that's the IDE not the compiler!
It's so that you buy more RAM, so that you feel the RAM usage of applications you are making, so that you make apps that take more RAM, so that other users use more RAM, so that users need more RAM, so that they buy more RAM. it's a kind of virus.
Or you can use /usr/bin/nano in Terminal.app ...
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
-
chris clepper -
IOhannes m zmoelnig -
Mathieu Bouchard