Hello,
Why isn't there the following in cmGlobalGenerator.h :
virtual const char* GetCleanTargetName() { return 0; }
and the following in cmGlobalUnixMakefileGenerator3.h :
virtual const char* GetCleanTargetName() { return "clean"; }
The reason I ask is because I needed f
why do I have to include and link qt_dir and qt_libs when I set this
variable ?
SET ( QT_USE_OPENGL TRUE )
INCLUDE_DIRECTORIES (
${CMAKE_CURRENT_BINARY_DIR}
${QT_INCLUDE_DIR}
${QT_QTOPENGL_INCLUDE_DIR}
)
T
works like a charm.
Thanks,
Marie
Michael G. Hansen wrote:
If I understand you correctly, you want to check whether the
FindQGLViewer found what it was looking for?
There should be no need to turn the file into a macro. Once you do
# Additional CMake modules for 3rd party library checks re
Marie-Christine Vallet wrote:
Michael G. Hansen wrote:
Marie-Christine Vallet wrote:
I wanted to check for an non standard existing library (QGLViewer)
and found a custom .cmake file on Internet that will do that for me.
The problem is that I am starting cmake, and do not know where to
place
Alexandru Ciobanu wrote:
> You are right. The patch does not do the right thing.
> I just observed that it also completely removes the
> preinstall rule for excluded directories.
>
> So make install insde those dirs will fail because there
> is no preinstall.
>
> Alexander Neundorf wrote:
>>
>> I
On 2007-08-03 10:27-0700 Alan W. Irwin wrote:
I would appreciate comment from the X experts here about whether the
proposed simplification would break any X platform that exists today. The
attached patch should serve as a concrete basis for discussion of such
simplification, and I have verified
Michael G. Hansen wrote:
Marie-Christine Vallet wrote:
I wanted to check for an non standard existing library (QGLViewer)
and found a custom .cmake file on Internet that will do that for me.
The problem is that I am starting cmake, and do not know where to
place that custom .cmake file
I foun
Marie-Christine Vallet wrote:
I wanted to check for an non standard existing library (QGLViewer) and
found a custom .cmake file on Internet that will do that for me. The
problem is that I am starting cmake, and do not know where to place that
custom .cmake file
I found the custom .cmake file h
Hi,
I wanted to check for an non standard existing library (QGLViewer) and
found a custom .cmake file on Internet that will do that for me. The
problem is that I am starting cmake, and do not know where to place that
custom .cmake file
I found the custom .cmake file here:
http://www-id.imag.f
--- Begin Message ---
Hi everyone,
In order to combat the spam that has been plaguing our public bug
tracker, we've decided to merge to a different bug tracking tool called
Mantis. We have migrated all the old bug data over from phpBugTracker.
Note that, unlike phpBugTracker, in Mantis yo
On Friday 03 August 2007 13:27, Alan W. Irwin wrote:
> On Linux (at least for both my Debian and Ubuntu platforms), FindX11.cmake
> sets X11_INCLUDE_DIR to /usr/include;/usr/include;/usr/include.
>
> This triplication is an annoyance at least in the case where you are using
> SET_SOURCE_FILES_PROPE
On Linux (at least for both my Debian and Ubuntu platforms), FindX11.cmake
sets X11_INCLUDE_DIR to /usr/include;/usr/include;/usr/include.
This triplication is an annoyance at least in the case where you are using
SET_SOURCE_FILES_PROPERTIES to set the -I compiler flags (as we do for the
subset o
On Friday 03 August 2007 12:32, Eric Noulard wrote:
> 2007/8/3, Alexander Neundorf <[EMAIL PROTECTED]>:
...
> > How are srpms supposed to handle this ? The configure scripts may need
> > additional arguments, same for cmake here.
>
> I don't really know I think your spec file contains "standard" op
2007/8/3, Alexander Neundorf <[EMAIL PROTECTED]>:
> On Friday 03 August 2007 09:49, Christian Convey wrote:
> > On 8/3/07, Alexander Neundorf <[EMAIL PROTECTED]> wrote:
> > > Currently we are in the process of migrating from phpbugtracker to
> > > mantis, so better wait a few days until everything
2007/8/3, Christian Convey <[EMAIL PROTECTED]>:
> On 8/3/07, Eric Noulard <[EMAIL PROTECTED]> wrote:
Stange enough your guy doesn't want to improve
its own software distribution...
> But anyway, the net effect is that I need to do as much outside of his
> source tree as possible, including any in
On 8/3/07, Michal Čihař <[EMAIL PROTECTED]> wrote:
> Is there
> some workaround for this so that I can produce library and executable of
> same name in one build tree?
Your CMake *target* names must be unique inside your CMakeLists.txt.
Otherwise dependency checking would fail. But the name of th
Eric Noulard wrote:
2007/8/1, Alexander Neundorf <[EMAIL PROTECTED]>:
On Wednesday 01 August 2007 04:12, Miguel A. Figueroa-Villanueva wrote:
Update patch and source.
I committed it to cvs with only minor cosmetical changes.
Thanks you for that.
Would it be possible to h
On 8/3/07, Eric Noulard wrote:
> 2007/8/3, Bill Hoffman :
> > So, I don't want to fill the disk with these things.
> > Should I just remove the previous night, or maybe
> > only put them out every two weeks?
>
> I would say that keeping the last 2 successful builds should be more than
> enough
> f
On Friday 03 August 2007 09:49, Christian Convey wrote:
> On 8/3/07, Alexander Neundorf <[EMAIL PROTECTED]> wrote:
> > Currently we are in the process of migrating from phpbugtracker to
> > mantis, so better wait a few days until everything is working again as it
> > should.
>
> OK, will do.
>
> >
On 8/3/07, Eric Noulard <[EMAIL PROTECTED]> wrote:
> > So I've been trying to accomplish
> > packaging with as few changes to his own CMakeLists.txt files as
> > possible.
>
> Yes I understand, nonetheless CPack IS a cross platform tools
> just as CMake is.
>
> I wrote UseRPMTools such as it won't
On 8/3/07, Alexander Neundorf <[EMAIL PROTECTED]> wrote:
> Currently we are in the process of migrating from phpbugtracker to mantis, so
> better wait a few days until everything is working again as it should.
>
OK, will do.
>
> P.S. which feature ?
Request #1:
My project produces multiple Debia
2007/8/3, Bill Hoffman <[EMAIL PROTECTED]>:
> >
> > That would be a good idea.
> > This way anybody wanting to test a binary
> > snapshot build will be able to do it.
> >
> So, I don't want to fill the disk with these things.
Of course your are right.
> Should I just remove the previous night, o
2007/8/3, Christian Convey <[EMAIL PROTECTED]>:
> On 8/2/07, Eric Noulard <[EMAIL PROTECTED]> wrote:
> > If you have trouble with the macro do not hesitate to ask for
> > explanation and/or send patched version either on the list or the wiki
>
> Thanks. Could you explain something to me?
>
> It lo
Eric Noulard wrote:
2007/8/3, Bill Hoffman <[EMAIL PROTECTED]>:
I think binary snapshot may be useful to widen testing?
I may contribute intel linux built if you find it both
feasible and useful.
I will see what I can setup for this. The build process for the
releases is automated,
2007/8/3, Christian Convey <[EMAIL PROTECTED]>:
> On 8/3/07, Eric Noulard <[EMAIL PROTECTED]> wrote:
> > > But when I do this, I don't find any files named
> > > CPackSourceConfig.cmake in my build directory ('x').
> >
> > Did you
> >
> > INCLUDE(CPack) in your root CMakeLists.txt ?
>
> Nope :) Th
On 8/3/07, Eric Noulard <[EMAIL PROTECTED]> wrote:
> > But when I do this, I don't find any files named
> > CPackSourceConfig.cmake in my build directory ('x').
>
> Did you
>
> INCLUDE(CPack) in your root CMakeLists.txt ?
Nope :) That fixed it.
The project I'm helping to package is lead by a guy
On Friday 03 August 2007 09:03, Christian Convey wrote:
> Is there somewhere I can register a feature request for CMake?
>
> I looked at the bug tracker, but got the sense that it was really
> meant for bugs, not feature requests.
Yes, it's also for features.
You can also post patches there :-)
Y
Is there somewhere I can register a feature request for CMake?
I looked at the bug tracker, but got the sense that it was really
meant for bugs, not feature requests.
- Christian
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listin
On 8/2/07, Eric Noulard <[EMAIL PROTECTED]> wrote:
> If you have trouble with the macro do not hesitate to ask for
> explanation and/or send patched version either on the list or the wiki
Thanks. Could you explain something to me?
It looks to me like you're supposed to be in the top-level direct
2007/8/3, Bill Hoffman <[EMAIL PROTECTED]>:
> >
> > I think binary snapshot may be useful to widen testing?
> > I may contribute intel linux built if you find it both
> > feasible and useful.
> >
> I will see what I can setup for this. The build process for the
> releases is automated,
I was sur
Hi
On Fri, 3 Aug 2007 10:25:59 +0200
"Eric Noulard" <[EMAIL PROTECTED]> wrote:
> Another Forget cc CMake-ML...
>
> Complement: When using other CMake macro you should use
> the primary name e.g:
>
> TARGET_LINK_LIBRARY(gammu-exe Gammu-Lib)
I found this myself meanwhile ;-).
> You should (for
Another Forget cc CMake-ML...
Complement: When using other CMake macro you should use
the primary name e.g:
TARGET_LINK_LIBRARY(gammu-exe Gammu-Lib)
-- Forwarded message --
From: Eric Noulard <[EMAIL PROTECTED]>
Date: 3 août 2007 10:23
Subject: Re: [CMake] MSVC project names
To:
What results in having two projects in MSVC both with same name (as
project names are not case sensitive) and this obviously fails. Is there
some workaround for this so that I can produce library and executable of
same name in one build tree
Hello,
I'm not sure but you can try to make 2 d
Hi
I'm using CMake on Gammu project [1] and now when first user wants to
natively compile it using MSVC on Windows I came to problems because
both library and executable projects share same name. Currently result
of build process is libGammu library and gammu program. This is
basically done by fol
2007/8/1, Alexander Neundorf <[EMAIL PROTECTED]>:
> On Wednesday 01 August 2007 04:12, Miguel A. Figueroa-Villanueva wrote:
> > Update patch and source.
>
> I committed it to cvs with only minor cosmetical changes.
Thanks you for that.
Would it be possible to have "some"
downloadable CMake CVS ve
35 matches
Mail list logo
