Bill Hoffman wrote:
Looks like a nice patch that you can put in your cmakelist files. I
still do not think it should go in CMake. I don't think that things
built by cmake that are native windows things belong in the /usr/local
mount point of msys. If you do, it is easy enough to change yo
Hello,
There is a bug 5007 (http://www.cmake.org/Bug/view.php?id=5007) to
which I think I have a patch for solving the issue, but I don't have
an OSX platform available for testing. I was going to apply the patch
since it seems pretty straight forward, but I'm inclined to wait until
somebody tests
I have created a feature request #5920 for the following issue. I
won't apply the changes myself unless I'm assigned the feature, since
I don't want to abuse my cvs modules access.
On 10/19/07, Alex Neundorf wrote:
> On Thursday 18 October 2007 21:25, Miguel A. Figueroa-Villanueva wrote:
> > - cre
Hi,
Currently FindQt4.cmake provides the path where the Qt4 installation has
put its own plugins, apparently to fulfil a bugreport that was filed
where somebody wanted to install a plugin.
Now this directory completely circuumvents CMAKE_INSTALL_PREFIX and
makes it impossible to install a Qt4-ba
On 10/19/07, Fernando Cacciola <[EMAIL PROTECTED]> wrote:
> Is there any hyperlinked (and preferably indexed) command reference?
There's the book "Mastering CMake."
Electronically, nope. It would be nice. We've discussed doc
improvement strategies in the past few months on this mailing list,
bu
Hi Mike,
When I try CMAKE_BUILD_TYPE MATCHES Debug, it seems to never execute
the contents of that IF statement (as if I am never CMake'ing a DEBUG
build?).
I don't know if CMAKE_BUILD_TYPE is the same thing as what's in the
CMAKE_CONFIGURATION_TYPES field. I really need something like:
IF (CMAK
Hello,
In a previous thread discussion
(http://www.cmake.org/pipermail/cmake/2007-October/017020.html) the
following issue arose and I'm asking this as a separate thread so it
can be noticed; as suggested by Alex.
There is a variable that I'm using named ImageMagick_EXECUTABLE_DIR.
Initially I th
Quoting [EMAIL PROTECTED]:
Hi,
On Friday 19 October 2007 01:18, Pau Garcia i Quiles wrote:
Hello,
As I told yesterday, here comes a patch for the Eclipse CDT4 generator
available in the current CVS version of CMake.
Although I have not extensively tested it, the works fine. In addition
to th
On 2007-10-20 22:26+0200 Mathias Baumann wrote:
Hi there,
I got a lib (icu), this lib provides also a icu-config script/binary which
tells me the compiler/linker flags..
So i can use icu-config --ldflags to find out the parameter for the linker.
And here comes the problem. How can i either pas
On 10/19/07, Alex Neundorf wrote:
> On Thursday 18 October 2007 21:25, Miguel A. Figueroa-Villanueva wrote:
> > On 10/14/07, Alex Neundorf wrote:
> > > On Saturday 13 October 2007 07:17, Miguel A. Figueroa-Villanueva wrote:
> > > > Hello,
> > > >
> > > > I've been assigned the task of maintaining t
The problem is only how to pass the parameters to the linker..
add_custom_command does not help me in passing sth to the linker, or am i
wrong here?
On 10/20/07, Mathias Baumann <[EMAIL PROTECTED]> wrote:
Hi there,
I got a lib (icu), this lib provides also a icu-config script/binary
which
On 10/19/07, Gonzalo Garramuño <[EMAIL PROTECTED]> wrote:
>
> a) All unix autotools utilities (or other libs like ffmpeg) built under
> mingw/msys will not install in $PROGRAMFILES, which leads to cmake's
> approach being totally backwards with the rest of msys.
Actually, last I checked 2+ years a
On 10/19/07, Gonzalo Garramuño <[EMAIL PROTECTED]> wrote:
> Brandon Van Every wrote:
> >
> > Agreed, having gone through this debate awhile ago. I would further
> > note that MinGW doesn't require MSYS, and that one would of course
> > expect %ProgramFiles% as the default in that case. Adding MSY
On 10/20/07, Mathias Baumann <[EMAIL PROTECTED]> wrote:
> Hi there,
> I got a lib (icu), this lib provides also a icu-config script/binary which
> tells me the compiler/linker flags..
> So i can use icu-config --ldflags to find out the parameter for the linker.
> And here comes the problem. How can
Gonzalo Garramuño wrote:
Bill Hoffman wrote:
But hey CMake is open source, you can always add the code you want by
yourself.
Here it is... I put some questions in the comments as I'm not that
familiar with the subtleties of some cmake's commands.
You probably want to clean it up. Took me
Hi there,
I got a lib (icu), this lib provides also a icu-config script/binary which
tells me the compiler/linker flags..
So i can use icu-config --ldflags to find out the parameter for the linker.
And here comes the problem. How can i either pass these parameters to the
linker, or extract th
Bill Hoffman wrote:
But hey CMake is open source, you can always add the code you want by
yourself.
Here it is... I put some questions in the comments as I'm not that
familiar with the subtleties of some cmake's commands.
You probably want to clean it up. Took me too long to write (love
Thanks Stefan.
When I do that, I see the following text in the Preprocessor
Definitions field (in vc++ 2005):
",WIN32,WINDOWS,"
I'm wondering if the leading and trailing commas will be a problem?
Thanks,
Mark
On 10/20/07, Stefan Buschmann <[EMAIL PROTECTED]> wrote:
> Use ADD_DEFINITIONS:
>
Use ADD_DEFINITIONS:
ADD_DEFINITIONS(-DWIN32 -DWINDOWS)
- Stefan
Mark Wyszomierski schrieb:
Hi,
How do we define a preprocessor statement - in win32 projects you
usually need to see the following in the C/C++ -> Preprocessor
statements section:
_WIN32, _WINDOWS ...etc
so in the CM
Hi,
How do we define a preprocessor statement - in win32 projects you
usually need to see the following in the C/C++ -> Preprocessor
statements section:
_WIN32, _WINDOWS ...etc
so in the CMakeLists.txt, what syntax is used to put that into the
generated project files?
Thanks,
Mark
Hello,
I just want to make a point here that usually the CMake developers
(Bill included) make every effort to tailor CMake to the users needs
and that this is simply something that, although controversial, is the
way it is supposed to be. That is, I would have to agree with Bill
here.
More below
Gonzalo Garramuño wrote:
Andreas Pakulat wrote:
But exactly that is not supposed to happen.
Why not? Maybe I was not clear:
cmake2.5 has a "MSYS Makefile" generator.
I did -G "MSYS Makefile" and I got an install on $PROGRAMFILES. That's
not correct.
If I wanted to install in $PROGRAMFIL
On 20.10.07 06:17:56, Gonzalo Garramuño wrote:
> Andreas Pakulat wrote:
> >But exactly that is not supposed to happen.
>
> Why not? Maybe I was not clear:
Or maybe I didn't read that part of the thread :)
> cmake2.5 has a "MSYS Makefile" generator.
Aah, ok. I take back all I said. The MSYS Ma
Andreas Pakulat wrote:
But exactly that is not supposed to happen.
Why not? Maybe I was not clear:
cmake2.5 has a "MSYS Makefile" generator.
I did -G "MSYS Makefile" and I got an install on $PROGRAMFILES. That's
not correct.
If I wanted to install in $PROGRAMFILES, there's NMake Makefile
Bill Hoffman wrote:
>
> Not really true, cygwin has its own symlinks. See here:
> http://www.cygwin.com/cygwin-ug-net/using.html
That's not a symlink. That's a mount point.
And it does not effect anything I said. Just try putting such a mount
point on PATH (which is special). It will get tr
On 19.10.07 20:12:54, Gonzalo Garramuño wrote:
> Bill Hoffman wrote:
>
> >There is no way to tell at cmake time what the user intends to use the code
> >for. If the user of cmake is building a windows app, which is the standard
> >use case for MinGW, then it you don't want /usr/local.
>
> I d
26 matches
Mail list logo
