cmSystemTools.cxx:(.text+0x62f): undefined reference to
`cmELF::cmELF(char const*)'
cmSystemTools.cxx:(.text+0x63d): undefined reference to `cmELF::GetRPath()'
cmSystemTools.cxx:(.text+0x65a): undefined reference to `cmELF::GetRunPath()'
cmSystemTools.cxx:(.text+0xa0f): undefined reference to `cmEL
Hi Randal,
you could use wgcc a cross-compiler tool
http://interix-wgcc.sourceforge.net/features.html
which should allow to use the msvc compiler in cygwin. But, I have no
experience with the Cygwin/MSVC/wgcc combination though.
Regards,
Werner
On 06.03.2008, at 00:00, Randal Walser wrote
Ben Ratzlaff wrote:
I have not gotten the Cygwin CMake to work well (its been a year since
I last tried) with Visual Studio. I have to download the one from
cmake.org. Then I use the following commands from a shell script
The Cygwin CMake works well with cygwin tools. You need to use the
nati
Quoting Christopher Harvey <[EMAIL PROTECTED]>:
Pau Garcia i Quiles wrote:
Quoting Bill Hoffman <[EMAIL PROTECTED]>:
Mike Jackson wrote:
In CMake CVS there is a Qt 4.x based GUI in development. I use it
on a daily basis on OS X and it is quite nice.
If you compile CMake from CVS, there
Pau Garcia i Quiles wrote:
Quoting Bill Hoffman <[EMAIL PROTECTED]>:
Mike Jackson wrote:
In CMake CVS there is a Qt 4.x based GUI in development. I use it
on a daily basis on OS X and it is quite nice.
If you compile CMake from CVS, there is an option to compile the
QtGUI. Look for it in
On Thursday 06 March 2008, Pau Garcia i Quiles wrote:
> Quoting Bill Hoffman <[EMAIL PROTECTED]>:
> > Mike Jackson wrote:
> >> In CMake CVS there is a Qt 4.x based GUI in development. I use it
> >> on a daily basis on OS X and it is quite nice.
> >>
> >> If you compile CMake from CVS, there is an o
Quoting Bill Hoffman <[EMAIL PROTECTED]>:
Mike Jackson wrote:
In CMake CVS there is a Qt 4.x based GUI in development. I use it
on a daily basis on OS X and it is quite nice.
If you compile CMake from CVS, there is an option to compile the
QtGUI. Look for it in the ccmake. It is not comp
On Wed, Mar 5, 2008 at 4:00 PM, Randal Walser <[EMAIL PROTECTED]> wrote:
>
> Can anyone tell me how I can use cmake to generate GNU makefiles which
> invoke the MSVC compiler? The Cygwin version of cmake seems to insist
> on gcc. Likewise, when I specify "Unix Makefiles" to CMakeSetup, it
> r
Mike Jackson wrote:
In CMake CVS there is a Qt 4.x based GUI in development. I use it on a
daily basis on OS X and it is quite nice.
If you compile CMake from CVS, there is an option to compile the QtGUI.
Look for it in the ccmake. It is not compiled by default (AFAIK).
If you are using C
In CMake CVS there is a Qt 4.x based GUI in development. I use it on
a daily basis on OS X and it is quite nice.
If you compile CMake from CVS, there is an option to compile the
QtGUI. Look for it in the ccmake. It is not compiled by default (AFAIK).
--
Mike Jackson
imikejackson & gmail *
I was talking to a friend about different build systems. We both like
CMake but we are unable to find a gui for it. (Other than the ncurses
one) It's not terribly important, mostly for fun really. Are there any
GUIs that use GTK or other for CMake?
thanks.
_
On Thursday 06 March 2008, Randal Walser wrote:
> Can anyone tell me how I can use cmake to generate GNU makefiles which
> invoke the MSVC compiler? The Cygwin version of cmake seems to insist
> on gcc. Likewise, when I specify "Unix Makefiles" to CMakeSetup, it
> resets the compiler to gcc after
Can anyone tell me how I can use cmake to generate GNU makefiles which
invoke the MSVC compiler? The Cygwin version of cmake seems to insist
on gcc. Likewise, when I specify "Unix Makefiles" to CMakeSetup, it
resets the compiler to gcc after I've set it to cl. Perhaps I'm
overlooking something,
On Wednesday 05 March 2008, Hendrik Sattler wrote:
> Am Mittwoch 05 März 2008 schrieb Alexander Neundorf:
> > attached you can find a patch which installs a freedesktop desktop file
> > for cmake-gui together with an icon, so that cmake should appear in the
> > start menus of KDE, Gnome, etc. (test
Mathieu Malaterre wrote:
anyone knows what happen with cmake 2.4.8 on cygwin ?
http://cygwin.com/packages/cmake/
Thanks
I have not sent a 2.4.8 to them. I will work on it...
Sorry...
-Bill
___
CMake mailing list
CMake@cmake.org
http://www.cmake.
anyone knows what happen with cmake 2.4.8 on cygwin ?
http://cygwin.com/packages/cmake/
Thanks
--
Mathieu
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Apologies. I tried again using the MFC dialog version of cmake and all
works well. I see that even though I did a make clean, the QtDialog
version was not rebuilt and I used that one to generate the files. All
is OK if I stick to the old style cmake exe.
JB
I just
upgraded to cmake 2.4.8 with
Am Mittwoch 05 März 2008 schrieb Alexander Neundorf:
> attached you can find a patch which installs a freedesktop desktop file for
> cmake-gui together with an icon, so that cmake should appear in the start
> menus of KDE, Gnome, etc. (tested with KDE 3.5)
>
> I'm not sure if the desktop file shoul
On Wednesday 05 March 2008, John Biddiscombe wrote:
> I just upgraded to cmake 2.4.8 with a clean copy from cmake website,
> cleaned my paraview tree and did a build. I now get all this. It's the
> STATIC build issue that troubles me (though there are poblems with
> vtk/utilities/encodestring too
I just upgraded to cmake 2.4.8 with a clean copy from cmake website,
cleaned my paraview tree and did a build. I now get all this. It's the
STATIC build issue that troubles me (though there are poblems with
vtk/utilities/encodestring too - I had to coment out EXPORT in
cmakelists). Any ideas wh
On Wednesday 05 March 2008, Jörg Becker wrote:
> On Tuesday 04 March 2008 22:10, Alexander Neundorf wrote:
> > Indeed, with cmake 2.4.6 and 2.4.8 "." is expanded to the current dir,
> > with cmake cvs HEAD it stays "." in the executable (is this then actually
> > relative to the location of the exe
On Tuesday 04 March 2008 22:10, Alexander Neundorf wrote:
> Indeed, with cmake 2.4.6 and 2.4.8 "." is expanded to the current dir, with
> cmake cvs HEAD it stays "." in the executable (is this then actually
> relative to the location of the executable or to the current working
> directory ?)
It is
On Wednesday 05 March 2008, Miguel A. Figueroa-Villanueva wrote:
...
> promote it for inclusion into CMake the author would need to open a
> mantis feature request and submit it for review from the community or
> maybe some official maintainers committee selected by the kitware
> folks or whatever.
On Wednesday 05 March 2008, packadal wrote:
> Ok, this way my build works, but the thing is the library i'm trying to
> compile is quite large, and putting the whole source list in a single file
> may make it hard for later modifications...
Which problems do you see ?
You could also put files in
Mike Jackson wrote:
Is there an archive of the video from this session?
Not yet. It will be available in a view days.
http://ftp.heanet.ie/mirrors/fosdem-video/2008/maintracks/
-- andreas
-- Mike Jackson Senior Research Engineer
Innovative Management & Technology Services
Sorry for the lame suggestion, then... I have not yet used git personally,
so I'm not up to speed on git command lines.
On 3/5/08, Brad King <[EMAIL PROTECTED]> wrote:
>
> David Cole wrote:
> > With this declarative style script, the inner ctest run via
> > CTEST_COMMAND will use the CVSCOMMAND c
Brad King wrote:
David Cole wrote:
With this declarative style script, the inner ctest run via
CTEST_COMMAND will use the CVSCOMMAND cache entry... CTEST_CVS_COMMAND
is used when you use the CTEST_UPDATE() command within a command-based
script (as opposed to a declarative script). Try adding:
C
Thanks a lot David!
Seems my 2003 didn't include the path variable, but at home my 2005 does.
Thanks again
On 05/03/2008, David Cole <[EMAIL PROTECTED]> wrote:
> In the Visual Studio IDE, go to "Tools > Options > Projects and Solutions >
> VC++ Directories" and inspect the value for Win32 Execu
David Cole wrote:
> With this declarative style script, the inner ctest run via
> CTEST_COMMAND will use the CVSCOMMAND cache entry... CTEST_CVS_COMMAND
> is used when you use the CTEST_UPDATE() command within a command-based
> script (as opposed to a declarative script). Try adding:
>
> CVSCOMMAN
Is there an archive of the video from this session?
--
Mike Jackson Senior Research Engineer
Innovative Management & Technology Services
On Feb 24, 2008, at 4:46 AM, Andreas Schneider wrote:
Hi Hackers,
at 12:00 CET you can watch Bill's talk [1] about CMake at the
FOSDEM [2].
[1] h
On behalf of Julien, Dave, Ken, Brad, Zack, Patrick, myself and the many
others that have contributed to the new CDash dashboard system, I am
happy to announce CDash Beta. CDash is a follow on effort to Dart1 and
Dart2. It uses many of the concepts that have been developed over the
past decad
With this declarative style script, the inner ctest run via CTEST_COMMAND
will use the CVSCOMMAND cache entry... CTEST_CVS_COMMAND is used when you
use the CTEST_UPDATE() command within a command-based script (as opposed to
a declarative script). Try adding:
CVSCOMMAND:STRING=/usr/bin/git-clone
t
On Wed, Mar 5, 2008 at 12:55 AM, Philip Lowman wrote:
> On Tue, Mar 4, 2008 at 12:39 PM, Sebastien BARRE wrote:
> > At 3/3/2008 03:34 PM, Matt Williams wrote:
> >
> > >I'm looking to see what you guys on this list think about me starting up
> > >a 'cmake community' site, possibly featuring the foll
Hi,
has someone CTest running with git? I can clone the repository, but it always
tries to use cvs to update. See attached config file.
-- andreas
--
http://www.cynapses.org/ - cybernetic synapses
set(CTEST_SOURCE_DIRECTORY "/tmp/testing/csync/nightly/source/")
set(CTEST_BINARY_DIRE
In the Visual Studio IDE, go to "Tools > Options > Projects and Solutions >
VC++ Directories" and inspect the value for Win32 Executable Files
directories.
You can add "$(PATH)" as the last entry in that box, or explicitly add the
directory to perl.exe.
In VS 2005 and later, MS puts $(PATH) there
The problem is that I don't call perl directly... It is being called
from within the openssl sources...
I can find perl perfectly with the FindPerl script, but somehow the
add custom command doesn't take the PATH variable into account when
running...
On 05/03/2008, Bill Hoffman <[EMAIL PROTECTE
Steven Van Ingelgem wrote:
Hi,
I am under Windows (VS2003).
If I run "ADD_CUSTOM_COMMAND", does the "COMMAND" run like a "cmd"
environment? In particular looking at the PATH variable?
I ask this because the output of my script indicates it cannot find
"perl", which is perfectly accessible bec
Hi,
I am under Windows (VS2003).
If I run "ADD_CUSTOM_COMMAND", does the "COMMAND" run like a "cmd"
environment? In particular looking at the PATH variable?
I ask this because the output of my script indicates it cannot find
"perl", which is perfectly accessible because I added it to the
enviro
38 matches
Mail list logo
