Then, is there any configuration setting that could influence the regex
behavior ?
- Kris
> -Original Message-
> From: Brad King [mailto:[EMAIL PROTECTED]
> Sent: vrijdag 30 juni 2006 19:24
> To: Kris Dekeyser
> Cc: 'cmake@cmake.org'
> Subject: Re: [CMake] Regex changes between cmake 2
Le Vendredi 30 Juin 2006 18:26, David Somers a écrit :
> I had a situation where a tool would always regenerate a h file... I fudge
> the issue now by caching the file and only replace it if diff says the file
> really is different (opposed to just being newer).
>
Hi, I have kindof similar situati
Luca Cappa wrote:
FIND_PACKAGE(wxWindows)
MESSAGE ("${wxWindows_FOUND}")
The variabel names are case sensituv.
WXWINDOWS_FOUND
Jan.
--
Dipl.-Ing. Jan Woetzel
--
University of Kiel
Institute of Computer Science and Applied Mathematics
Herma
Hello,
i have a little problem with latest stable cmake. My cmakelists.txt file is
FIND_PACKAGE(wxWindows)
MESSAGE ("${wxWindows_FOUND}")
IF(NOT wxWindows_FOUND)
MESSAGE(FATAL_ERROR "
even if the find_package is successfull, the wxWindows_FOUND is always a
blank variable, it is ne
On Mon, 03 Jul 2006 11:26:56 +0200, Jan Woetzel
<[EMAIL PROTECTED]> wrote:
Luca Cappa wrote:
FIND_PACKAGE(wxWindows)
MESSAGE ("${wxWindows_FOUND}")
The variabel names are case sensituv.
WXWINDOWS_FOUND
Sorry, but i do not get what case sensitiveness counts here: the docs says:
"_FOUND w
On 7/3/06, Luca Cappa <[EMAIL PROTECTED]> wrote:
Maybe the variable _FOUND is required to be defined by the .cmake
file? in that
case it is my fault, since i wrote that package finder :)
That is the case. The Find*.cmake module must implement some standard
behaviour, which is assumed by the hel
On Mon, July 3, 2006 11:13 am, Benjamin THYREAU wrote:
>> I had a situation where a tool would always regenerate a h file... I
>> fudge the issue now by caching the file and only replace it if diff says
>> the file really is different (opposed to just being newer).
>>
> Hi, I have kindof similar si
On Mon, 03 Jul 2006 12:29:09 +0200, Miguel A. Figueroa-Villanueva
<[EMAIL PROTECTED]> wrote:
On 7/3/06, Luca Cappa <[EMAIL PROTECTED]> wrote:
Maybe the variable _FOUND is required to be defined by the .cmake
file? in that
case it is my fault, since i wrote that package finder :)
That is the
Kris Dekeyser wrote:
I just ran your example with 2.4.2 and got the latter output.
Then, is there any configuration setting that could influence the regex behavior ?
No. Did you build CMake 2.4.2 yourself or use a pre-compiled binary?
-Brad
___
CMa
Brad,
I grabbed the binaries from the download web page last friday.
When I run the simple test below, it's fine.
CMakeLists.txt
SET(WordList "D:Temp;c:/;/root;relpath;subdirone")
MACRO(PRINT_MESSAGE DebugLevel Message)
MESSAGE(STATUS "${Message}")
ENDMACRO(PRINT_MESSAGE)
Hi Brad,
Yep, I just discovered what it is. The WordList entry actually starts with a
${var}. The text is read from a project configuration file with
FILE(READ ${Configfile} ConfigFileContents)
When a [Headers] section is encountered, each line is processed. One of these
lines contain:
${EDA_RO
Folks,
In the VXL project, we use FIND_PACKAGE to allow internal code to use
the public VXL code. As currently set up, this causes a call to
CMAKE_IMPORT_BUILD_SETTINGS, which in turn checks that the internal
project uses the same generator, compiler, and compiler flags as the
external project.
I
Hi Brad,
I'm pretty sure something changed in the the interpretation of variables. I
attached a simple CMakeLists.txt file that shows the difference along with a
configuration file to read in.
In Cmake 2.0.6 it runs fine. In Cmake 2.4.2 it fails when reading the
configuration file. The backsla
This is a story post, and a thank-you post.
I recently built the CVS version of CMake for the first time, and then went
on to package it into a "personal binary distro" using CPack (and NSIS).
Here's how I did it.
I fetched the CVS version of CMake, and used my installed binary version of
CMake
Amitha Perera wrote:
In the VXL project, we use FIND_PACKAGE to allow internal code to use
the public VXL code. As currently set up, this causes a call to
CMAKE_IMPORT_BUILD_SETTINGS, which in turn checks that the internal
project uses the same generator, compiler, and compiler flags as the
exter
Kris Dekeyser wrote:
I'm pretty sure something changed in the the interpretation of variables. I
attached a simple CMakeLists.txt file that shows the difference along with a
configuration file to read in.
Yes, this did change, but the original behavior was not intended or
documented. Note t
Can someone suggest a good way to copy a data directory from the source tree
to the build tree?
I want to be do this for both Unix and VC builds.
The purpose is just to have some test input data available in the location
where the newly built program is looking for it.
Hi!I'm a Visual Basic programmer (yes Visual Basic) with a lot of free time.VB file can be made with a command line (and can be linked with VC 2003 toolkit, but not it's important)
It's possible to make a new generator for CMake for Visual Basic (classic version)?What I need to start? it's easy to
I have put ADD_DEFINITIONS(-DCMAKE_BUILD) in CMakeLists.txt and
statements such as #if !defined(CMAKE_BUILD) in my .h files. Is there a
canonical definition for this? I didn't see any canonical flag being
passed to the C compiler, so I'm guessing there isn't one, but I have a
vague memory of
19 matches
Mail list logo
