On Thursday 20 September 2007 20:38:38 Juan Sanchez wrote:
It appears that the set command cannot override a variable specified as
a MACRO argument.
For example:
MACRO (ADD_GADB RCMD)
does not accept changes to RCMD within the macro using the set command.
Is there a way to override this?
On 9/21/07, Andrew Maclean [EMAIL PROTECTED] wrote:
Is it worthwhile putting in a backwards compatible fix for such an old
version of wxWidgets?
grunt
This has been broken in patch version ! cmake 2.4.5 / 2.4.6 / 2.4.7
are completely different in wx support.
At least put a warning when you
On 9/20/07, Christian Buhtz [EMAIL PROTECTED] wrote:
What is the difference between cmake and bakefiles?
http://bakefile.sourceforge.net/wiki/index.php?n=Bakefile.Comparisons
CMake is the most similar to Bakefile from these. It generates
semi-native makefiles -- while the makefile is for the
Actually I have just begun using version 2.8.5 of wxwidgets. Miguel could
you please patch it to also use this version? I would thik you just need to
add wxWidgets-2.8.5 at line 376 beforewxWidgets-2.8.4
It would be much appreciated.
Thanks
Andrew
On 9/21/07, Mathieu Malaterre
2007/9/7, Eric Noulard [EMAIL PROTECTED]:
2007/9/7, Mathieu Malaterre [EMAIL PROTECTED]:
I have had some issue with recent CMake version since the wxWidget
script broke backward compatibility. AFAIK the find script only works
with very recent wxWidget.
what is your wxWidget version ?
Hello list,
I am new to cmake and I have just read the FAQ
http://www.cmake.org/Wiki/CMake_FAQ#Distribution_questions
I have also studied the CPack documentation, but I am still wondering
the following:
CMake doesn't create a make dist target.
Does this simply mean that there is no target
Hello Eric,
thank you very much for your very quick response. Yes, I am willing to
write some documentation on the Wiki as soon as I have understood the
basic principles of how to make a package.
Eric Noulard wrote:
Write you CMakeLists.txt
make it work for:
1 - compiling your project
On Friday 21 September 2007 14:55:43 Joachim Ziegler wrote:
Hello Eric,
I'll drop in and try to answer the questions.
2 - installing your project (i.e. no error when calling 'make
install')
This does not. I have no target install. Browsing through
On Friday 21 September 2007 04:31, Mathieu Malaterre wrote:
On 9/20/07, Christian Buhtz [EMAIL PROTECTED] wrote:
What is the difference between cmake and bakefiles?
http://bakefile.sourceforge.net/wiki/index.php?n=Bakefile.Comparisons
CMake is the most similar to Bakefile from these. It
I ask me why there are so much make-implementations. It is to hard for
all of us. I know that there couldn't be the one super-make...
Can CMake read a foreign-makefile (e.g. MinGW-make or nmake) and
generate its own cmake-makefile of it (what is the word for the
cmake-makefile-format?)?
Or
Hello Dizzy,
Dizzy wrote:
So you said you want some package made of some files, but a package means some
files that eventually will be on the system in some locations (when the
package is installed) so with cmake INSTALL() commands you specify how are
those files to be installed (if the user
Mathieu Malaterre schrieb:
CMake is the most similar to Bakefile from these. It generates
semi-native makefiles -- while the makefile is for the native make
tool, it still requires presence of CMake during compilation. Bakefile
has no such requirement.
You mean if I generate a MinGW-makefile
On Friday 21 September 2007 08:34, Christian Buhtz wrote:
Mathieu Malaterre schrieb:
CMake is the most similar to Bakefile from these. It generates
semi-native makefiles -- while the makefile is for the native make
tool, it still requires presence of CMake during compilation. Bakefile
has
On Friday 21 September 2007 08:37, Christian Buhtz wrote:
I ask me why there are so much make-implementations. It is to hard for
all of us. I know that there couldn't be the one super-make...
That's what cmake is for. Write it once for cmake, which hides all the
differences of the different
On 21.09.07 14:26:58, Joachim Ziegler wrote:
Dizzy wrote:
So you said you want some package made of some files, but a package means
some
files that eventually will be on the system in some locations (when the
package is installed) so with cmake INSTALL() commands you specify how are
Let me try to clarify some terminology.
The source tree is where source files (*.c, etc.) and configuration files
(CMakeList.txt, etc.) live.
The build tree is where you build the software. It contains everything that
is configured or built. It's got a lot of files in it (e.g., *.o) that are
Alexander Neundorf schrieb:
cmake does the dependency scanning and rules for rerunning cmake are included
in the makefiles.
How do I build my source (with a cmakefile in it) for MinGW on WinXP?
What is the command for that?
I thougt I have to do something like cmake generate-my-gcc-makefile
Juan Sanchez wrote:
What I was trying to do was to avoid having to create a local variable.
The macro parameter is the default, which can be overridden if necessary.
Now I immediately have to set a new variable with the value of the
parameter. So I now have to account for another variable
On Friday 21 September 2007 12:29, Christian Buhtz wrote:
Alexander Neundorf schrieb:
cmake does the dependency scanning and rules for rerunning cmake are
included in the makefiles.
How do I build my source (with a cmakefile in it) for MinGW on WinXP?
What is the command for that?
I
I would argue that the following snippet of code should either print
CAT twice or die. Unfortunately it first prints DOG and then CAT.
Thanks,
Juan
MACRO(FOO BAR)
SET (BAR CAT)
MESSAGE(${BAR})
ENDMACRO(FOO)
FOO(DOG)
MESSAGE(${BAR})
Bill Hoffman wrote:
Juan Sanchez wrote:
What I was
Hi,
I am trying to convert my group's existing Visual Studio project to using
CMake to support multiple platform development. For that purpose I am trying
to get Visual Studio solutions and project files to be as similar as
possible to the ones my group is currently using so that the
Ok,
But cpp doesn't discriminate between ${BAR} and BAR.
#include iostream
using namespace std;
#define foo(x) x = 3; cout x \n;
int main()
{
int y = 1;
foo(y);
cout y endl;
}
Juan
Bill Hoffman wrote:
Juan Sanchez wrote:
I would argue that the following snippet of code should
Juan Sanchez wrote:
Ok,
But cpp doesn't discriminate between ${BAR} and BAR.
#include iostream
using namespace std;
#define foo(x) x = 3; cout x \n;
int main()
{
int y = 1;
foo(y);
cout y endl;
}
I said like cpp, not exactly cpp. The difference is you have to use ${} to
expand
Hello,
How do you add an externally library for linking into a target? I am
getting something like this from TARGET_LINK_LIBRARIES?
CMake Error: Attempt to add link library /bar/linux-x86/opt/foo.a to
target waterlooApps which is not built by this project.
Thanks,
Juan
On 09/21/2007 10:15 PM, Juan Sanchez wrote:
Hello,
How do you add an externally library for linking into a target? I am
getting something like this from TARGET_LINK_LIBRARIES?
CMake Error: Attempt to add link library /bar/linux-x86/opt/foo.a to
target waterlooApps which is not built by this
On Saturday 22 Sep 2007 1:45:26 am Juan Sanchez wrote:
How do you add an externally library for linking into a target? I am
getting something like this from TARGET_LINK_LIBRARIES?
CMake Error: Attempt to add link library /bar/linux-x86/opt/foo.a to
target waterlooApps which is not built by
26 matches
Mail list logo
