If it helps, I tried this and QT4 installed fine for me following the instructions in their README file. Basically I did this:
1. Unzip and untar to desktop
2. CD into resulting directory
3. ./configure -universal
4. make
5. sudo make install
6. Add:
PATH=/usr/local/Trolltech/Qt-4.2.2/bin:$PATH
export PATH
to ~/.profile
I then compiled and installed exiv2 according to the instructions in their README - unzip, untar, cd to resulting directory and:
1. ./configure --without-zlib (because there was some other dependency I didn't want to fool with just to see if I could get this compiled.)
2. make
3. sudo make install
All of that appeared to go well.
Now when I went to compile qtpfsgui I got past the qmake stage OK (after changing the location of exiv2 to match the OSX path in the project.pro file as the instructions required).
At that point I went to make qtpfsgui and I get this:
src/hdrcreate/createhdr.cpp:15: error: 'open_memstream' was not declared in this scope
make: *** [generated_obj/createhdr.o] Error 1
At that point the code looks like:
Code:
#ifdef _WIN32
void createHDR(QList<QImage*> &list, const float * arrayofexptime, config_triple* chosen_config, bool antighosting, int iterations, const char * outfname) {
FILE *fpout=fopen(outfname,"wb");
#else
QByteArray createHDR(QList<QImage*> &list, const float * arrayofexptime, config_triple* chosen_config, bool antighosting, int iterations){
//prepare "fake" FILE* where pfs library will write the output hdr to, in pfs stream format.
char *pfshdr;
size_t size;
FILE * fpout=open_memstream(&pfshdr, &size);
#endif
So we're getting into the unix-specific code correctly and it's failing there. I'm not sure why - maybe open_memstream has some trick to it on OSX. Hopefully this is enough of a clue for someone else to spot what's going on.
Anyway, I didn't get the whole thing working but I can say that QT4 appears to install fine for me on an Intel Mac (for anyone else who wants to try this, be forewarned that building it takes a good long time) so with any luck you'll be able to get over that hurdle. It was necessary to read the documentation to catch that I had to specify the flag for a universal build and that I needed to add QT to my path so if you didn't do that, that may have been your QT problem.
