Bill -
I looked through the `Mastering Cmake` bible, and Web page Still a bit
confused about that VS 2003 case:
1. When I run my executables test1, test2, test3... from within VS 2003 IDE
- they manage to find foo.dll. Even though it is not within "Visual Studio
PATH" but only within my 're
Michael Andronov wrote:
Hi, Bill -
First, I'm apologizing for my last question - the answer was too
obvious, I should found it in a manual. :)
So, my `problem
No problem, it is not exactly obvious where to find it. :)
-Bill
___
CMake mailin
Hi, Bill -
First, I'm apologizing for my last question - the answer was too obvious,
I should found it in a manual. :)
So, my `problem
On Sat, May 24, 2008 at 2:15 PM, Bill Hoffman <[EMAIL PROTECTED]>
wrote:
> Michael Andronov wrote:
>
>> Hi, Bill:
>>
>> Yes, following your advice, I managed
Eduardo Alberto Hernández Muñoz wrote:
CMake complains about not finding the file before creating the makefile.
-Coz
This works for me just fine:
message(STATUS "checking openal version")
TRY_RUN (
OPENAL_VERSION_1_1
OPENAL_COMPILED
${CMAKE_BINARY_DIR}
${CMA
Hi
>> I'm trying to add a version check to the FindOpenAL.cmake module.
>> Here's the relevant part:
>>
>>TRY_RUN (
>>OPENAL_VERSION_1_1
>>OPENAL_COMPILED
>>${CMAKE_BINARY_DIR}
>>${CMAKE_SOURCE_DIR}/check_openal_version_1_1.cpp
>>)
>>
>> A simple 'g++ ch
Eduardo Alberto Hernández Muñoz wrote:
Hi list,
I'm trying to add a version check to the FindOpenAL.cmake module.
Here's the relevant part:
TRY_RUN (
OPENAL_VERSION_1_1
OPENAL_COMPILED
${CMAKE_BINARY_DIR}
${CMAKE_SOURCE_DIR}/check_openal_version_1_1.cpp
Hi list,
I'm trying to add a version check to the FindOpenAL.cmake module.
Here's the relevant part:
TRY_RUN (
OPENAL_VERSION_1_1
OPENAL_COMPILED
${CMAKE_BINARY_DIR}
${CMAKE_SOURCE_DIR}/check_openal_version_1_1.cpp
)
A simple 'g++ check_openal_version_
Michael Andronov wrote:
Hi, Bill:
Yes, following your advice, I managed to adjust manually the directories
within 2003, and it works.
I still failed to find the registry record - VS registry record - to
do it by my installation script.
Back to cmake. Is it possible to detect while execut
Michael Andronov wrote:
Bill,
Thank you very much for the speedy reply.
When you install VS, it copies the PATH as it was during install.
You are probably partially right.
In my case, root/kernel/bin/Release is added to my PATH during the
installation of my foo project.
In both cases -
Michael Andronov wrote:
...
4. cmake run with no problem indication;
5. When VS 2003 is opened, the projects are built with no problem
indication.
So far everything behaved as expected. Now, the `unexplained' started:
u.1. Attempt to build RUN_TESTS project within VS 2003 finishes with
Hi,
I have `un explained` behavior of CTest and VS 2003...
Let me formulate the problem briefly:
1. I have a project, consisting of foo.dll and 4 executables, using it;
2. the structure of the project is:
root/
kernel/bin/Release/foo.dll
test1/bin
test2/bi
Dario Figueira schrieb:
I would like to have the CMake GUI up and running in my debian OS, and
for that i need to install "curses libraries"..
None of the packages available with the "apt-get" are obviously the
ones needed, so i'm unsure what to install.
I tried downloading "ncurses" from GNU, b
Hello,
I would like to have the CMake GUI up and running in my debian OS, and for
that i need to install "curses libraries"..
None of the packages available with the "apt-get" are obviously the ones
needed, so i'm unsure what to install.
I tried downloading "ncurses" from GNU, but when reading the
Bill Hoffman wrote:
Mathieu Malaterre wrote:
Hum... I tried again today and I cannot reproduce it. So to properly
find wxWidgets on my machine I need to get rid of all entries in the
PATH_SUFFIXES section.
I would love to get rid it of that nasty bug before the next release
of cmake, so could
Mathieu Malaterre wrote:
Hum... I tried again today and I cannot reproduce it. So to properly
find wxWidgets on my machine I need to get rid of all entries in the
PATH_SUFFIXES section.
I would love to get rid it of that nasty bug before the next release
of cmake, so could the maintainer of wxW
Quoting Eduardo Alberto Hernández Muñoz <[EMAIL PROTECTED]>:
Hi,
I am wondering if there is a way to disable checking that the ELSE and
ENDIF arguments need to the the same as the initial IF. For example,
[...]
This is the default in CMake 2.6, you don't need to specify the statement in
the e
Hum... I tried again today and I cannot reproduce it. So to properly
find wxWidgets on my machine I need to get rid of all entries in the
PATH_SUFFIXES section.
I would love to get rid it of that nasty bug before the next release
of cmake, so could the maintainer of wxWidgets stand up and tell me
On Fri, May 23, 2008 at 5:46 PM, Brad King <[EMAIL PROTECTED]> wrote:
> Blezek, Daniel J., Ph.D. wrote:
>>
>> I'd like to build and install Insight (though the toolkit is not
>> important) using GCC. Then I want to build applications using GCC, the
>> Intel compiler, and IBM's XLC compiler. All
On Sat, May 24, 2008 at 12:46 AM, Eduardo Alberto Hernández Muñoz <
[EMAIL PROTECTED]> wrote:
> Hi,
>
> >> I am wondering if there is a way to disable checking that the ELSE and
> >> ENDIF arguments need to the the same as the initial IF. For example,
> > [...]
> > This is the default in CMake 2.6
Alan W. Irwin wrote:
On 2008-05-23 22:43-0400 Bill Hoffman wrote:
This is the default in CMake 2.6, you don't need to specify the
statement in the endif.
If you do specify something, is it checked?
e.g., will CMake-2.6.0 continue to find badly nested if statements
like
if(whatever0)
if(what
20 matches
Mail list logo
