Hi,
On Fri, Jun 22, 2012 at 6:33 AM, hce wrote:
>
> Andreas Pakulat-2 wrote
> >
> > You can find extensive explanation where find_path works on the different
> > platforms in the CMake documentation:
> > http://cmake.org/cmake/help/v2.8.8/cmake.html#command:find_path
> >
>
> Thanks Andreas, but
Andreas Pakulat-2 wrote
>
> You can find extensive explanation where find_path works on the different
> platforms in the CMake documentation:
> http://cmake.org/cmake/help/v2.8.8/cmake.html#command:find_path
>
Thanks Andreas, but I am not looking for how to use find_path command. What
I really
Thanks, Eric.
I had plans for adding find_library. I have seen a fair amount about how this
is more idiomatic but little about what the disadvantages are in the short run
of using an environment variable directly while building up the system.
Perhaps I chose a wrong incremental pathway to get
On Thu, Jun 21, 2012 at 11:33 AM, Yuri Timenkov wrote:
> Is it strict requirement? Can't you just add your .rc files as source
> file to your target or just add target name as part of file name? This
> way they can be put everywhere, including current binary dir. I use
> this for adding version in
Yes, you have to be running a nightly build of CMake. 2.8.8 does not
use relative paths in VS2010 projects.
On Thu, Jun 21, 2012 at 3:17 AM, Klaim - Joël Lamotte wrote:
> Hi, I'm having the same problem with a project generated with CMake 2.8.8 to
> VS2010 open with VS2012 RC.
>
>
> On Wed, Jun 1
Hi,
I was wondering if there is a best practice for providing a file for user
configuration decisions (options, unique flags) that will be more persistent
than the cache? I have a project where a dozen or two algorithmic decisions
have to be made. I find that this is just enough that cache overw
2012/6/21 Bill Lorensen :
> Probably in the documentation for the install command:
>
> The COMPONENT argument specifies an installation component name with
> which the install rule is associated, such as "runtime" or
> "development". During component-specific installation only install
> rules assoc
Is it strict requirement? Can't you just add your .rc files as source
file to your target or just add target name as part of file name? This
way they can be put everywhere, including current binary dir. I use
this for adding version information to binaries.
Otherwise you may try to use post-build
>From reading this, I get the distinct impression that your are not
>interpreting the meaning of "nightly" in the same way that the rest of us are
>doing so.
Let's assume the following:
At 15 minutes past each hour, a new commit is added to the repository.
For the sake of description, the "zer
I really want to do that, but unless I can add source files to a target
after its been created, I'm in a catch 22:
I need the location of that directory to place a resource file there, which
will be included in the target. HOWEVER-
I can't get the location without creating the target, and I can't
This is becoming a challenge :-)
I'm generating .RC files using configure_file() in my CMake script. Since I
can have multiple targets defined in the same directory, and the resource
file generated for each target has the same name, I need them to be placed
in the .dir directory inside of CMAKE_CU
I was thinking of same problem also and it would be good to have
common switch in CMake which translates into generator-specific
parameter (actually CMAKE_BUILD_TOOL's one, btw you can get it with
from CMakeCache.txt).
Our builds broke couple of times when CMake jumped between devenv and
msbuild fo
I'm not sure but this may be "feature" of msbuild: it doesn't rescan
dependencies after run. This causes a lot of troubles with generated
code (for same reason auto-reloading macro doesn't work since VS2010).
You may try to work this around by splitting build into several stages
(i.e. adding custo
Then you should use LOCATION target property
(http://www.cmake.org/cmake/help/v2.8.8/cmake.html#prop_tgt:LOCATION)
or use generator expressions, because exact place where resulting
binary located depends on many things (used generator, other
variables, like CMAKE_RUNTIME_OUTPUT_DIR, etc).
On Thu,
This is a limitation of CMake. There is a discussion at
http://public.kitware.com/Bug/view.php?id=11899
On Tue, Jun 19, 2012 at 7:57 PM, Michele Santullo
wrote:
> Hello, we recently converted our project to cmake but for some reason, as we
> generate for VS 2008 on Windows, we get the same path f
Hi all,
I want to be able to build 32-bit and 64-bit from the same GCC multilib install
(currently for MinGW-w64, though this also applies for Linux/Mac GCC and LLVM).
To clarify, I want to be able to do two completely separate builds in
separate binary dirs - building fat binaries from multi
On Thu, Jun 21, 2012 at 9:26 AM, Robert Dailey wrote:
> You're totally confused. I'm not looking to work around a problem, I just
> want information from CMake that I know it has. Somewhere it knows exactly
> where binaries will be placed (those binaries that get compiled) because it
> has to gene
You're totally confused. I'm not looking to work around a problem, I just
want information from CMake that I know it has. Somewhere it knows exactly
where binaries will be placed (those binaries that get compiled) because it
has to generate the scripts and visual studio projects with those paths
in
Take a look here:
https://gitorious.org/pclsuperbuild/pclsuperbuild
I recently created this superbuild for the Point Cloud Library. You'll
see that it configures and builds Boost with be. Also it downloads
PCL, configures and builds it and other dependencies.
It is new,, so there may be some issu
On Thu, Jun 21, 2012 at 8:58 AM, Robert Dailey wrote:
> So how do I get the absolute path to this directory in a portable (between
> generators) way?
>
>
Well, what is it you want from there? I generate INSTALL commands to
put the outputs where I want them and let them worry about where the
file
So how do I get the absolute path to this directory in a portable (between
generators) way?
On Thu, Jun 21, 2012 at 9:03 AM, J Decker wrote:
> On Wed, Jun 20, 2012 at 12:08 PM, Robert Dailey
> wrote:
> > ${CMAKE_CURRENT_BINARY_DIR} returns a directory that contains generated
> > files, such as
Well I could use this in combination with get_file_component() to get just
the filename, right? Is Location a directory path, or does it include the
EXE in the path as well?
On Wed, Jun 20, 2012 at 1:48 PM, David Cole wrote:
> Yes, with:
>
> http://cmake.org/cmake/help/v2.8.8/cmake.html#prop_t
On 18. Jun 2012, at 20:03, Knox, Kent wrote:
> That is an interesting approach; if this 'superbuild' cmake project
> downloaded and built all the external dependencies first, then my project
> could find those dependencies with the appropriate find module? I suppose
> that the 'superbuild' co
If you want to find a library, then use find_library. find_path is for *any*
type of file, and only matches on file name, find_path does not know anything
special about libraries. find_library does know some special stuff about
libraries (like to look for them in directories listed in the LIB a
2012/6/21 hce :
> Hi,
>
> There were some discussions to fix %config at
> http://public.kitware.com/Bug/view.php?id=10294. But I tried to use
> CPACK_RPM_SPEC_IGNORE_FILES in 2.8.8, it does not seem work. What is current
> situation to use %config?
This should definitely work in 2.8.8 for RPM, how
Probably in the documentation for the install command:
The COMPONENT argument specifies an installation component name with
which the install rule is associated, such as "runtime" or
"development". During component-specific installation only install
rules associated with the given component name w
Eric,
My bad. I see all three components if the target includesan
executable, static lib and shared lib.
Thanks,
Bill
On Thu, Jun 21, 2012 at 2:38 AM, Eric Noulard wrote:
> 2012/6/21 Bill Lorensen :
>> According to the documentation, an install command like this:
>> INSTALL (
>> TARGETS myT
Hi,
There were some discussions to fix %config at
http://public.kitware.com/Bug/view.php?id=10294. But I tried to use
CPACK_RPM_SPEC_IGNORE_FILES in 2.8.8, it does not seem work. What is current
situation to use %config? Even if the RPM variable works for %config, how
can the no replace files work
Hi,
On Thu, Jun 21, 2012 at 1:07 PM, hce wrote:
> Hi,
>
> I am running 2.8.8 on Linux. I have a library already been set up in
> environment, I can see it in both LD_LIBRARY_PATH and $PATH, but when I was
> compiling another source code which calling find_path() to check the
> library
> package
Hi,
I am running 2.8.8 on Linux. I have a library already been set up in
environment, I can see it in both LD_LIBRARY_PATH and $PATH, but when I was
compiling another source code which calling find_path() to check the library
package include path, it failed. In general, how the cmake find_path() t
Hi,
I am running 2.8.8 on Linux. I have a library already been set up in
environment, I can see it in both LD_LIBRARY_PATH and $PATH, but when I was
compiling another source code which calling find_path() to check the library
package include path, it failed. In general, how the cmake find_path() t
Hi, I'm having the same problem with a project generated with CMake 2.8.8
to VS2010 open with VS2012 RC.
On Wed, Jun 13, 2012 at 3:20 AM, Ben Medina wrote:
> - Using the VS2010 generator, the project files have relative paths.
> VS2012RC can load 2010 project files without modifying them. If I d
32 matches
Mail list logo
