Hi,
I add a test that needs to load a certain xml file and process its
content. The xml file is in the same directory as the test sources, in
the source tree. How can I install this xml file so that it will be
available in the binary tree, in the same directory as the test
executable?
Thanks!
--
Hi Brandon,
ccmake --version - ccmake version 2.4-patch 6
doxygen --version - 1.5.0
What about under ccmake 2.4.7, the current release?
Can you reproduce your problem in a short piece of code, i.e. a
trivial project using doxygen?
I have the same problem compiling ccmake 2.4.7! I guess
On Nov 22, 2007 4:42 AM, Fabian Wein
[EMAIL PROTECTED] wrote:
I installed ncurses_devel, removed the above message but not the problem.
I'm confused at this point what the problem is. Please don't skip
things you did, it makes it hard to figure out what's going on. i.e.
please cut paste
Bill Hoffman wrote:
You can also use the GNU make included here:
http://unxutils.sourceforge.net/
This is really just a (small) set of unix tools running natively under
Windows, using native Windows paths, etc. IMO this is the easiest way
to get GNU make for Windows.
Don't use the GNU
Hi,
I found the Problem (thanks Jan!). It did not work on a mounted
directory when logged it
on the fileserver itself. It works e.g. in /tmp on the fileserver.
Thanks for any help!
Regards, Fabian
___
CMake mailing list
CMake@cmake.org
Hello all,
After the run of ctest I need to access (by a script) to the Xml files
in ${CTEST_BINARY_DIR}/Testing/Tag, where tag is by default the
timestamp of the test.
Is there any solution to set this tag or to get its value in CTest ?
My script is based on the stable version of Ctest, where
On 2007-11-22 10:11+0200 Salvatore Iovene wrote:
Hi,
I add a test that needs to load a certain xml file and process its
content. The xml file is in the same directory as the test sources, in
the source tree. How can I install this xml file so that it will be
available in the binary tree, in the
Cmake seems to define, for each library that is built, a symbol
of the form library_EXPORTS, which can be used to set up
#defines for the __declspec(dllexport/dllimport) stuff that
Windows needs.
However, this means that each library needs a specific symbol
to allow it to be built with the
2007/11/23, Stephen Collyer [EMAIL PROTECTED]:
Cmake seems to define, for each library that is built, a symbol
of the form library_EXPORTS, which can be used to set up
#defines for the __declspec(dllexport/dllimport) stuff that
Windows needs.
However, this means that each library needs a
Eric Noulard schrieb:
2007/11/23, Stephen Collyer [EMAIL PROTECTED]:
Cmake seems to define, for each library that is built, a symbol
of the form library_EXPORTS, which can be used to set up
#defines for the __declspec(dllexport/dllimport) stuff that
Windows needs.
However, this means that
On Nov 22, 2007 5:40 PM, Alan W. Irwin [EMAIL PROTECTED] wrote:
Second, if it is really necessary in this case, then you can
CONFIGURE_FILE with the COPYONLY attribute at cmake time or execute
Hi, that fit me very well, thanks!
--
Salvatore Iovene
http://www.iovene.com/
Key Fingerprint: 5647
11 matches
Mail list logo
