Bug 71656 - Definition of minimal Qt version
Summary: Definition of minimal Qt version
Status: RESOLVED DUPLICATE of bug 69770
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: Automake (show other bugs)
Version: 3.0.0b2
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-02 09:09 UTC by Alexander Reinholdt
Modified: 2008-06-29 17:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Reinholdt 2004-01-02 09:09:30 UTC 
Version:           3.0.0b2 (using KDE 3.1.4)
Installed from:     (testing/unstable)
Compiler:          gcc version 3.3.2 (Debian)
OS:          Linux (i686) release 2.4.23

It is not possible to set the minimal Qt version for a project. I wanted to bump the Qt version from 3.1 to 3.2 for my project, but I could neither find this option in the project options (Project->Project Options...) nor in the Automake Manager. Or is this option hidden somewhere else? If yes, please move it to the project option dialog.

Cheers,
Alexander
Comment 1 Jens Dagerbo 2004-01-02 14:58:11 UTC 
If it doesn't exist, it isn't a bug. Sounds like a wish though. :)

Actually, isn't this a specific case of the general wish for creating configure tests?
Comment 2 Alexander Reinholdt 2004-01-02 15:52:08 UTC 
Yes, right. Configure tests would be really great.
Comment 3 Harald Fernengel 2004-01-02 17:56:31 UTC 
add the following line to configure.in.in:

#MIN_CONFIG(3.0.0)

replace 3.0.0 with the desired version.

A GUI entry for this would be nice, yes :)
Comment 4 Amilcar do Carmo Lucas 2004-06-25 21:27:12 UTC 
Harald I think your comment concerns the KDE version and not the Qt version
Comment 5 Andreas Pakulat 2008-06-29 17:13:19 UTC 
as said in the comments this is a special case of a general autoconf editor. closing as duplicate.

*** This bug has been marked as a duplicate of 69770 ***