[Slackbuilds-users] Slackbuild for QT3 only app

[Slacker build user]

Niels Horn wrote:
> On Thu, Jun 3, 2010 at 7:42 PM, Slacker build user
> <slacker at slaphappygeeks.com> wrote:
>> Hello,
>>
>> I am finally getting my few packages updated to 13.1, and adding a new one I
>> hope.
>>
>> I am building Bouml from http://bouml.free.fr/ which requires Qt3. It builds
>> fine against Eric's kde3 compat Qt3 package on both 32 and 64 (not
>> multi-lib) boxes. But I have two questions:
>>
>> 1. I have to pass a properly set QTDIR variable so it can find the Qt3 libs.
>> Is there a preferred method of testing and exiting if this is not set? Or
>> should it be hard-wired into the build script?
>>
>> 2. The make files all use qmake and have the var QMAKE=qmake hard wired into
>> them in multiple places - which tries to use Qt4's qmake. It cannot use an
>> environment var to override the path to qmake. For my own builds I have
>> added a symlink /usr/local/bin/qmake => /opt/kde3/bin/qmake which I remove
>> when done.
>>
>> Any suggestions for a more elegant way to direct it to Qt3 qmake? Patch the
>> make files? Alias? Temporary symlink?
>>
>> Thanks,
>>
>> Robert
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
>>
>>
> 
> Hi,
> 
> I have built some packages that needed the Qt3 libs.
> 
> Usually you need to do some "hacking" in the Makefile (or
> <your-program>.pro) to guarantee the use of the Qt3 programs like
> qmake, moc, assistant, etc. Just include the full path to the Qt3
> programs, like /opt/kde3/bin/qmake /opt/kde3/bin/uic etc.
> 
> Niels

So you are saying to modify the make files in the source tree. Would some simple 
sed changes to the make files be acceptable in an SBo script? (I just answered 
that by looking in some others... DUH!)

OK, I'll verify the QTDIR variable and exit with suitable message, and do a 
little sed and see if I can make it painless.

Thanks Niels,

Robert