Josh Cherry wrote:
> 1. The slowness depends (in part, at least) on the fact that there is a
> cont.end() call for every iteration. If the code is changed to look like
> this:
>
> cont_end = cont.end()
> while it != cont.end():
> it.next()
>
> it is much faster. Of course,
Jesper Eskilson wrote:
2007/5/18, Joshua Jensen <[EMAIL PROTECTED]>:
Custom build types don't work under Visual Studio. The following
"patches" (not really a patch but the best I could do at the moment)
gives you custom build types under Visual Studio. These are against
latest CVS.
This isn't
2007/5/18, Joshua Jensen <[EMAIL PROTECTED]>:
Jesper Eskilson wrote:
> Hi all,
>
> I tried following the instructions on the wiki on how to define my own
> build type (configuration), however the new build type ("Develop")
> does not show up as a valid solution configuration in Visual Studio.
> W
Jesper Eskilson wrote:
Hi all,
I tried following the instructions on the wiki on how to define my own
build type (configuration), however the new build type ("Develop")
does not show up as a valid solution configuration in Visual Studio.
Why is that?
Custom build types don't work under Visual S
gga wrote:
Bill Hoffman wrote:
Can you send a small example that does not work with nmake?
Not too small, I'm afraid. Is it okay to post a zip to the list? Or
to send you one?
You can send me something off the list.
I think I'm running into 2 or 3 issues, from what I can te
Bill Hoffman wrote:
> Can you send a small example that does not work with nmake?
>
Not too small, I'm afraid. Is it okay to post a zip to the list? Or
to send you one?
I think I'm running into 2 or 3 issues, from what I can tell from the
verbose logs. Here's what I have:
Under NMake Makef
Hi All,
I wanted to from my top level directory do something like
make internal or make release.
Now depending on what I specify I need certain others files(not part of
install) to be modified or left alone. Can I define my own targets? mind you
these are not build types.
I have
INS
Hello, gga!
>> I don't think using MSVC programs in GNU Makefile is a very good idea
>> because they (linker in paticular) are not GNU-compatible by flags and
>> arguments.
>
> ...
>
> I would like to run microsoft's CL.exe, LIB.exe, etc. tools, but from
> within a Unix GNU Makefile. A makefile
Hi all,
I tried following the instructions on the wiki on how to define my own
build type (configuration), however the new build type ("Develop")
does not show up as a valid solution configuration in Visual Studio.
Why is that?
--
/Jesper
___
CMake mai
Hi.
I've been using CMake and Dart2 to do simple builds for some time.
It's great!
However, I have a few things that are "hacks" rather than something
that looks nice.
I'd like to clean it up.
I would appreciate it if anyone can point me to examples where
someone has addressed a similar
Guilherme Balena Versiani wrote:
> I have a big software distribution with several third-party software
> bundled with it. I use CMake to download these third-party packages,
> unpack, configure and install it temporarily in a CMAKE_BINARY_DIR
> subdir (e.g. ${CMAKE_BINARY_DIR}/dist) -- after this
Hi, I use cmake under windows, with both gfortran (gnu fortran) and ifort
(intel fortran) compilers.
I have found some problems that I would like to put at your attention.
1) the default intel fortran installation set two environment variables FFLAGS
and F90FLAGS, with the following value:
/w /
gga wrote:
Nikita V. Borodikhin wrote:
Hello, Gonzalo!
I don't think using MSVC programs in GNU Makefile is a very good idea
because they (linker in paticular) are not GNU-compatible by flags and
arguments.
Thanks for the help. Still struggling, thou, due to nmake's crappy system.
Cristian Adam wrote:
Please update your findboost.cmake with the changes the original
poster made, by
adding boost-1.34 (and others) to SUFFIX_FOR_PATH.
Done.
I have also submitted these changes as a feature request
http://public.kitware.com/Bug/bug.php?op=show&bugid=5057&pos=0
Regards,
Mik
Mike Talbot wrote:
I have made some enhancements to FindBoost.cmake to try to add support
for the boost libraries (attached).
Thanks, the enhancements are welcome, the script now looks like this:
project(signal CXX)
if (MINGW)
set(Boost_LIB_SUFFIX mgw34-s-1_34)
set(Boost_LI
I have made some enhancements to FindBoost.cmake to try to add support
for the boost libraries (attached).
Basic use is something like this:
FIND_PACKAGE(Boost)
INCLUDE_DIRECTORIES(${Boost_INCLUDE_DIRS})
ADD_EXECUTABLE(signal signal.cpp)
TARGET_LINK_LIBRARIES(signal ${Boost_signal_LIBRARIES})
Nikita V. Borodikhin wrote:
> Hello, Gonzalo!
>
> I don't think using MSVC programs in GNU Makefile is a very good idea
> because they (linker in paticular) are not GNU-compatible by flags and
> arguments.
>
Thanks for the help. Still struggling, thou, due to nmake's crappy system.
Sorry, also
Nikita V. Borodikhin wrote:
> Hello, Gonzalo!
>
> I don't think using MSVC programs in GNU Makefile is a very good idea
> because they (linker in paticular) are not GNU-compatible by flags and
> arguments.
>
Thanks for the help. Still struggling, thou, due to nmake's crappy system.
Sorry, also
Bob Kuehne wrote:
boost recently updated to 1.34, changing (of course) the default
installation path. this breaks the FindBoost cmaker, so attached is an
update that allows 1.34 as released to work.
Regarding FindBoost.cmake, I'm testing Boost 1.34.0 with MinGW gcc 3.4.2
MinGW doesn't have a
I have some questions about the process by which the INSTALL() command
works:
---
Despite CMAKE_BUILD_TYPE being set to Debug in CMakeSetup for my NMake
project, cmLocalGenerator::GenerateInstallRules() creates
cmake_install.cmake files with a default line of
SET(CMAKE_INSTALL_CONFIG_NAM
Hello, Gonzalo!
gga wrote:
> Okay, first time trying cmake under windows, porting a project from linux.
> ...
> Also, is there a way to avoid this annoying gui and just use cmake
> command-line and have it create an nmake Makefile (or, better yet, a
> normal GNU makefile using cl.exe and ld.exe a
21 matches
Mail list logo
