Hi Den,

A note for future releases, there are 3 places on the file create_framework.sh (or similar name) where the Qt version number appears. If one is using different Qt versions, you have to change those places to your version. It would be nice if those occurences are substituted by a variable, so you have only one place to change, avoiding searching in the file.

thanks,

Have you tried latest svn updates for mac ? :)

Felipe Monteiro de Carvalho wrote

those places to your version. It would be nice if those occurences are substituted by a variable, so you have only one place to change,

ok

Tiny detail:

Now on 1.52 compile and create_framework.sh no longer come already with 755 permission so you can run the script on bash.

thanks,

Felipe Monteiro de Carvalho wrote

Now on 1.52 compile and create_framework.sh no longer come already with 755 permission so you can run the script on bash.

should be done

Felipe,

Excellent idea. Not sure how I missed that. My instructions here:

http://wiki.lazarus.freepascal.org/Qt_Interface_Mac#Creating_the_Qt_inte rface_framework

mention changing the QT4 variable in the script, but the version also needs to be changed in two other places as well.

Thanks.

-Phil

Philip J wrote

those places to your version. It would be nice if those occurences are substituted by a variable, so you have only one place to change,

Please create better and tested (I do not have a Mac) version of these files and send these to me. I will update then update my generator.

Since your last request these files have become
string constants with %s (filled in with QT_VERSION)

...
PListFile=$FmwkFolder/Versions/A/Resources/Info.plist Qt4=../qt-mac-opensource-src-%s
Qt4Core=$Qt4/lib/QtCore.framework/Versions/4/QtCore ...

This reminds me of something I kinda forgot. Too much multi-tasking. Mario offered packaging support. Do you think it would be easier with cmake stuff or so? If there would be someone, more experienced than me with make files, who can contact him and see how things could be easier (compiling the library source and/or installing the library.) The generator itself is too manually to start from.

regards,

Den Jean

Den,

Not sure what you mean by "packaging support"? Do you mean supplying a standard Lazarus .lpk file that, when compiled, creates the interface library (and framework under OS X)?

Thanks.

-Phil

Am Donnerstag, 11. Oktober 2007 18:30:20 schrieben Sie:

Not sure what you mean by "packaging support"? Do you mean supplying a standard Lazarus .lpk file that, when compiled, creates the interface library (and framework under OS X)?

my support would be in a better buildsystem for the lib based on cmake

no bash scripts and the qt4 location is autodetected take a look at the patch it is the first version of this buildsystem (still without generating sources from qt4 headers)

and as i read in the qt archive a bash script is used to create the macosx framework for this lib i will add support for deb, rpm, packagebuilder (macosx) in the next version of the build system.

Mario

------------------------------------------------------- -------------- next part --------------
A non-text attachment was scrubbed...
Name: qt4pas-1.5.3-cmake_build-1.patch
Type: text/x-diff
Size: 6303 bytes
Desc: not available
URL: <http://lists.lazarus.freepascal.org/pipermail/qt/attachments/20071011/9aab574c/attachment.bin> -------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.lazarus.freepascal.org/pipermail/qt/attachments/20071011/9aab574c/attachment-0001.bin>

Mario Fetka wrote

my support would be in a better buildsystem for the lib based on cmake

What is cmake?

felipe2:~ felipemonteirodecarvalho$ cmake
-bash: cmake: command not found

If this requiring installing additional software I would rather being able to choose which build system to use.

Felipe Monteiro de Carvalho wrote

What is cmake?

take a look at http://www.cmake.org

it is also the standard buildsystem for kde4 that will also be present on windows OS X

it is multiplatform

is a makefile generator

and it is normally already included in most linux Dists

Mario
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.lazarus.freepascal.org/pipermail/qt/attachments/20071011/01bc81f7/attachment.bin>

Mario,

cmake is not present on Windows and I doubt if it's on OS X either (not at my Mac right now).

The trickiest part of creating the Qt interface library and framework on OS X is step 2 in my instructions:

http://wiki.lazarus.freepascal.org/Qt_Interface_Mac#Creating_the_Qt_libr aries_from_Qt_Open_Source_Edition

Steps 3 and 4, which use scripts, are pretty brainless to use. I'm not sure what problem cmake would solve by replacing them. Perhaps you could just modify the two scripts so they auto-detect the location of the Qt open source, although usually if folks can successfully create the Qt libraries in step 2, then they're capable of modifying the scripts.

Thanks.

-Phil

Not that I am going to build qt myself, t doesn't seem to be too widespread. Four *nix hosts, I use for building Lazarus snapshots:

michael-ep3:~ fpcfan$ uname -a
Darwin michael-ep3.local 8.10.0 Darwin Kernel Version 8.10.0: Wed May 23 16:50:59 PDT 2007; root:xnu-792.21.3~1/RELEASE_PPC Power Macintosh powerpc michael-ep3:~ fpcfan$ cmake
-bash: cmake: command not found

vsds at amd300:~> uname -a
Linux amd300 2.6.16.13-4-default #1 Wed May 3 04:53:23 UTC 2006 i586 i586 i386 GNU/Linux
vsds at amd300:~> cmake
bash: cmake: command not found

fpcfan at amd64 ~ $ uname -a
Linux amd64 2.6.17-gentoo-r2 #1 SMP PREEMPT Sat Jul 8 19:27:04 EDT 2006 x86_64 A MD Athlon(tm) 64 Processor 3500+ AuthenticAMD GNU/Linux fpcfan at amd64 ~ $ cmake
-bash: cmake: command not found

fpcfan at scenergyng:~$ uname -a
Linux scenergyng 2.6.15-29-amd64-k8 #1 SMP PREEMPT Mon Sep 24 17:26:00 UTC 2007 x86_64 GNU/Linux
fpcfan at scenergyng:~$ cmake
-bash: cmake: command not found

And finally the fifth:
Schindlers-iMac:~ fpcfan$ uname -a
Darwin Schindlers-iMac.local 8.10.1 Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386 i386 i386 Schindlers-iMac:~ fpcfan$ cmake
cmake version 2.4-patch 6

Vincent

Philip J wrote

The trickiest part of creating the Qt interface library and framework on OS X is step 2 in my instructions:

Yes, it's tricky (and takes a lot of time to complete the build of Qt), but it only needs to be done once.

I already have create the framework. I have a directory called:

/Library/Frameworks/Qt4Intf.framework

And several frameworks related to Qt4. What should be distributed?

Only the Qt4Intf.framework? If so, in which format? A zip file?

Maybe we could distribute the Qt related frameworks too. Otherwise everyone using this framework would require building Qt.

Felipe,

If you used create_framework_mac.sh included with Den's .zip to create the Qt4Intf.framework, then no other Qt framework is required to run Laz apps that depend on it, as the script copies the Qt4Core and Qt4Gui libraries into the Qt4Intf.framework and fixes them up.

The proper way to distribute a framework with OS X is as an installation .dmg to ensure it's installed in the correct place. As I mentioned yesterday, I can contribute the PackageMaker file (.pmproj) that I used in the past to create .dmg's for Den.

Thanks.

-Phil

Philip J wrote

The proper way to distribute a framework with OS X is as an installation .dmg to ensure it's installed in the correct place. As I mentioned yesterday, I can contribute the PackageMaker file (.pmproj) that I used in the past to create .dmg's for Den.

That would be nice!

I'll look for some PackageMaker tutorials in the internet ... never really used it before

thanks,