Or are these customizing CPack command line options mostly meant to be
used with a CPACK_PROJECT_CONFIG_FILE?
On Thu, Sep 11, 2014 at 9:07 AM, Iosif Neitzke
wrote:
> For a project that uses include(CPack) and produces
> CPack_Example-0.1.1-Linux.sh when "cpack" is run and produces
> CPack_Example
Is there a significant amount of output from make? What does make do if
it's running low on RAM?
ctest may be holding onto "too much" memory trying to process the
output if it's very large...
Just a thought -- worth a look, though.
D
--
Powered by www.kitware.com
Please keep messages on-
On 9/11/2014 4:09 PM, Hennigan, Gary L wrote:
Thanks for the reply Chuck.
Do you have an external projects in this build?
-Bill
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to sup
On Thursday, September 11, 2014 23:51:21 Nico Schlömer wrote:
> Hi all,
>
> One of my projects contains two libraries libA and libB, where libB
> depends on libA, and both are exporting their configuration through
> the usual `INSTALL(EXPORT ...)` mechanisms.
> I'm getting errors of the type
> ```
Set the OUTPUT_NAME or OUTPUT_NAME_ property on the target to
change what the name of the generated library will be. This will
eliminate the need for a post-build step.
On Thu, Sep 11, 2014 at 4:16 PM, fungos wrote:
> Cool, this did the trick. It was needed a post-build step to rename the
> targe
Hi all,
One of my projects contains two libraries libA and libB, where libB
depends on libA, and both are exporting their configuration through
the usual `INSTALL(EXPORT ...)` mechanisms.
I'm getting errors of the type
```
CMake Error: install(EXPORT "SEACASNemesis-exports" ...) includes
target "n
Cool, this did the trick. It was needed a post-build step to rename the
target but it works.
Thank you
On Thu, Sep 11, 2014 at 2:19 PM, Chuck Atkins
wrote:
> Sounds like what you want is an object library,
> http://www.cmake.org/Wiki/CMake/Tutorials/Object_Library:
>
> set(FOO_SOURCES
> Foo1.c
Thanks for the reply Chuck.
Unfortunately there is no such message. I’m not even sure the GNU make
jobserver is the problem. It’s just that the symptom is the same as if that
were happening.
Am I comparing apples to apples when I go into the build directory created via
ctest and invoking gmake
Excuses; I found the target property setting in the respective
`myLibTargets-none.cmake` file:
```
set_target_properties(myLib PROPERTIES
IMPORTED_LINK_INTERFACE_LIBRARIES_NONE "/usr/lib/liblapack.so"
IMPORTED_LOCATION_NONE
"${_IMPORT_PREFIX}/lib/x86_64-linux-gnu/libmylib.so.1.0"
IMPORTED_SON
Hi Gary,
Do you see either of these two warning messages show up:
"warning: -jN forced in submake: disabling jobserver mode."
or
"warning: jobserver unavailable: using -j1. Add `+' to parent make rule."
These warnings often accompany the forced serialization of a parallel make
build, although us
I have a strange, and very frustrating, problem. I have a pretty large piece of
software that I build nightly as part of regression testing of my own software.
All of the software uses CMake and I use a ctest script, via "ctest -S [script
file]", for my nightly regression testing . As I stated,
Sounds like what you want is an object library,
http://www.cmake.org/Wiki/CMake/Tutorials/Object_Library:
set(FOO_SOURCES
Foo1.cxx
Bar2.cxx
FooBar3.cxx
)
add_library(FooObjLib OBJECT ${FOO_SOURCES})
add_executable(A $)
set_target_properties(A PROPERTIES LINK_FLAGS "/Special /Flags /For /A")
Ok, but will this _recompile_ the sources for each target? We must use the
same generated object files for the two outputs, the only difference must
be the linker flags.
On Thu, Sep 11, 2014 at 1:20 PM, Robert Maynard
wrote:
> Generally the easiest way is to have two targets that share the same
Generally the easiest way is to have two targets that share the same
source files but have different linker flags.
On Thu, Sep 11, 2014 at 12:53 PM, fungos wrote:
> Yes, we can say that.. in reality I need two outputs for a single target,
> but these outputs are generated almost exactly with just
Yes, we can say that.. in reality I need two outputs for a single target,
but these outputs are generated almost exactly with just 2 different linker
flags removed.
On Thu, Sep 11, 2014 at 11:31 AM, Robert Maynard wrote:
> Are you trying to generate two different libraries from the same target?
We are pleased to announce that CMake 3.0.2 is now available for download.
Please use the latest release from our download page:
http://www.cmake.org/download/
Thanks for your support!
-
Changes in 3.0.2 since 3.0.1:
Alan
Hi Greg,
You might want to check out our current fork of CMake on
http://cmakems.codeplex.com. I've just added support for multiplatform support
for Windows Phone and Windows Store app in a similar way that it is done for
iOS.
You can try the build on http://cmakems.codeplex.com/releases/view/
On 9/11/2014 7:04 AM, Ravi Raman wrote:
Yes. That's correct David. I was actually looking for an explanation
why the object file name is coming with the suffix .cpp.obj instead
of the conventional .obj. It was kind of a problem for me because the
object file comparison tool uses the object file n
Are you trying to generate two different libraries from the same target?
On Thu, Sep 11, 2014 at 10:45 AM, fungos wrote:
> Hi,
>
> How can I create two linker steps with different flags for the same target
> at the same build?
>
> Example:
>
> target: X
> link: linker.exe libs_for_a linker_
On Thu, Sep 11, 2014 at 9:51 AM, Vojtech Mašek wrote:
> Hi, I am working at team developing RPM pacage generator.
> Now I am solving a problem how can i get dependencies using cmake.
> Basically we need to get paths to libs like they are cached in
> CmakeCache.txt, is it somehow possible before c
Hi, I am working at team developing RPM pacage generator.
Now I am solving a problem how can i get dependencies using cmake.
Basically we need to get paths to libs like they are cached in
CmakeCache.txt, is it somehow possible before calling cmake and then
parsing the file ?
--
Powered by www.kit
Hi,
How can I create two linker steps with different flags for the same target
at the same build?
Example:
target: X
link: linker.exe libs_for_a linker_flags_for_a -o A/X.bin
link: linker.exe libs_for_b linker_flags_for_b -o B/X.bin
Thanks
--
Powered by www.kitware.com
Please keep
For a project that uses include(CPack) and produces
CPack_Example-0.1.1-Linux.sh when "cpack" is run and produces
CPack_Example-0.1.1-Linux.exe when "cpack -G NSIS" is run, am I remiss
for thinking that
cpack -G NSIS -P NEW_NAME -R 3.1.4
should produce "NEW_NAME-3.1.4-Linux.exe"?
As always, than
Hi all,
Ninja does not clean out non-empty directories.
Given this CMakeLists.txt:
==
cmake_minimum_required(VERSION 2.8)
add_custom_command(
OUTPUT dir
COMMAND ${CMAKE_COMMAND} -E make_directory dir
COMMAND ${CMAKE_COMMAND} -E touch dir/file
)
add_custom_target(
dir-target DEPENDS
Yes. That's correct David. I was actually looking for an explanation why the
object file name is coming with the suffix .cpp.obj instead of the conventional
.obj.
It was kind of a problem for me because the object file comparison tool uses
the object file name as the reference for object file co
I think (Ravi, correct me if I'm wrong) that they're transitioning to
CMake from a previously purely Visual Studio build system, and they're
writing some tools to validate that the builds are ending up "the same."
So it's not really a "problem" for anybody -- I think he was just
looking for an
On Thu, Sep 11, 2014 at 08:25:27AM +, Ravi Raman wrote:
>Actually, in our project, the names of the object files matter because
>these object files go as an input to a object file comparison tool that
>compares object file names. So, there are 2 sets of object files, one
>coming
Actually, in our project, the names of the object files matter because these
object files go as an input to a object file comparison tool that compares
object file names. So, there are 2 sets of object files, one coming from cmake
build and one from Visual Studio build.
The set coming from cmake
I was wondering about this as well. Ravi, what is your motivation for
having object file names of a particular format? I don't think I've ever
had to care what object files in our builds are called.
Petr
On Thu, Sep 11, 2014 at 10:01 AM, Andreas Mohr wrote:
> Hi,
>
> > Date: Thu, 11 Sep 2014 07
Hi,
> Date: Thu, 11 Sep 2014 07:49:23 +
> From: Ravi Raman
> Hi,
>
> Thanks Petr for your reply. By incorrect I meant instead of the conventional
> main.obj, we get main.cpp.obj.
> I understood what you are saying. We have found a solution for this in our
> cmake code.
Good, so you've fo
Hi,
Thanks Petr for your reply. By incorrect I meant instead of the conventional
main.obj, we get main.cpp.obj.
I understood what you are saying. We have found a solution for this in our
cmake code.
We have explicitly set the /Fo compiler flag for main.cpp. With that it creates
main.obj for mai
31 matches
Mail list logo
