Hello everyone,
I'm trying to set up an environment for building a pre-existing medium sized
embedded software project, by using CMake 2.8 and MinGW. The compiler kit is
specific for the target microcontroller and contains C compiler, assembler,
linker, all different executables.
I do have some r
On 08/02/2011 05:36 PM, David Cole wrote:
> When you do not have a ".app" directory, and you are not copying into
> the same directory with the executable, then the question in my mind
> becomes "what exactly is 'the bundle' at this point?"
>
> With a dir/bin, dir/lib typical Linux style layout, "d
On Tue, Aug 2, 2011 at 8:05 PM, Clinton Stimpson wrote:
>
> On Aug 2, 2011, at 5:47 PM, Gregory Crosswhite wrote:
>
>> On 8/2/11 4:32 PM, Clinton Stimpson wrote:
>>> There is no scanning the file system to find which libraries to fix up.
>>> Any libraries used by executables will be considered in
On Aug 2, 2011, at 5:47 PM, Gregory Crosswhite wrote:
> On 8/2/11 4:32 PM, Clinton Stimpson wrote:
>> There is no scanning the file system to find which libraries to fix up.
>> Any libraries used by executables will be considered in the set of libraries
>> to fix up, regardless of where they are
On 8/2/11 4:32 PM, Clinton Stimpson wrote:
There is no scanning the file system to find which libraries to fix up.
Any libraries used by executables will be considered in the set of libraries
to fix up, regardless of where they are installed (in bin/ or lib/). Any
libraries not found as a depend
On Tuesday, August 02, 2011 05:09:04 pm Gregory Crosswhite wrote:
> On 08/02/2011 03:10 PM, Clinton Stimpson wrote:
> > On Tuesday, August 02, 2011 03:38:01 pm Gregory Crosswhite wrote:
> > You need an @ONLY for configure_file() so it doesn't substitute the ${}
> > parts also.
>
> Doh! Thanks for
On Tuesday, August 02, 2011 03:38:01 pm Gregory Crosswhite wrote:
> On 8/2/11 1:09 PM, Clinton Stimpson wrote:
> > Ok, can you make an example that demonstrates the problem?
> >
> > I think this should work without overriding get_dotapp_dir() in
> > BundleUtilities.
>
> The example is attached to
Am Dienstag, 2. August 2011, 21:55:16 schrieb Alexander Neundorf:
> Hi,
>
> until recently, I recommended to install Config.cmake files more or less
> like this:
>
> install(FILES FooConfig.cmake DESTINATION lib${LIB_SUFFIX}/cmake/Foo )
>
> with LIB_SUFFIX being "64" on systems where this is req
Hi,
I agree with JC and will move the CTK discussion to the ctk-developers list.
Thanks,
Sascha
On 08/02/2011 05:21 PM, Jean-Christophe Fillion-Robin wrote:
Within CTK,
Where we are specifying a specific SHA1, we could set UPDATE_COMMAND
to be ""
Where we are specifying a branch like "orig
On 08/02/2011 01:28 PM, David Cole wrote:
Thanks for this info... I've reproduced the problem now, too. I'm not
sure what to do about it yet, but I can make it happen: that's the
first step toward a fix.
There should not be a need for an update step if you're snapped to
particular hash or non-t
Hi,
On Tuesday 02 August 2011, Glenn Coombs wrote:
> Previously with cmake 2.8.4 we were using these lines to compile an
with 2.8.5 there was a major rework of the assembler support (and now it
finally does not say "Assembler support is experimental" anymore).
Sorry that this causes inconvenienc
On Tuesday, August 02, 2011 02:03:23 pm Gregory Crosswhite wrote:
> On 8/2/11 12:53 PM, Clinton Stimpson wrote:
> > On Mac, are you making a .app bundle, or are you doing a layout similar
> > to Linux, with bin/, lib/ layout, or something else?
>
> The latter --- I was hoping to use a layout simil
On 8/2/11 12:53 PM, Clinton Stimpson wrote:
On Mac, are you making a .app bundle, or are you doing a layout similar to
Linux, with bin/, lib/ layout, or something else?
The latter --- I was hoping to use a layout similar to Linux with bin/,
lib/, etc. since the program is console-based and so
On 8/2/11 12:47 PM, David Cole wrote:
The "non .app dir" problem should go away if you use the recently
released CMake 2.8.5. This bug was fixed in that version:
http://public.kitware.com/Bug/view.php?id=12034
Thank you very much for the heads up, but I have already been running
CMake 2.8.5 al
Hi,
until recently, I recommended to install Config.cmake files more or less like
this:
install(FILES FooConfig.cmake DESTINATION lib${LIB_SUFFIX}/cmake/Foo )
with LIB_SUFFIX being "64" on systems where this is required.
How do I do this on a Debian multiarch system ?
How do I know in which di
On Tuesday, August 02, 2011 01:42:47 pm Gregory Crosswhite wrote:
> On 8/2/11 9:28 AM, Clinton Stimpson wrote:
> > You shouldn't need to copy GetPrerequisites and BundleUtilities.
> >
> > For Linux you can do:
> > set_target_properties( ... PROPERTIES INSTALL_RPATH "\$ORIGIN/../lib")
> >
> > To g
On Tue, Aug 2, 2011 at 3:42 PM, Gregory Crosswhite
wrote:
> On 8/2/11 9:28 AM, Clinton Stimpson wrote:
>>
>> You shouldn't need to copy GetPrerequisites and BundleUtilities.
>>
>> For Linux you can do:
>> set_target_properties( ... PROPERTIES INSTALL_RPATH "\$ORIGIN/../lib")
>>
>> To get /usr/lib/
On 8/2/11 9:28 AM, Clinton Stimpson wrote:
You shouldn't need to copy GetPrerequisites and BundleUtilities.
For Linux you can do:
set_target_properties( ... PROPERTIES INSTALL_RPATH "\$ORIGIN/../lib")
To get /usr/lib/ to be treated as non-system libraries, you can implement
gp_resolved_file_typ
On 8/2/11 9:28 AM, Clinton Stimpson wrote:
You shouldn't need to copy GetPrerequisites and BundleUtilities.
For Linux you can do:
set_target_properties( ... PROPERTIES INSTALL_RPATH "\$ORIGIN/../lib")
To get/usr/lib/ to be treated as non-system libraries, you can implement
gp_resolved_file_typ
On Monday, August 01, 2011 07:12:15 pm Gregory Crosswhite wrote:
> Hey everyone,
>
> I am using CMake to build a package which has the normal unix layout,
> i.e. programs are in bin/, libraries are in lib/, etc., and I would like
> to simply copy all of the required shared non-system libraries int
Previously with cmake 2.8.4 we were using these lines to compile an assembly
language file in our project:
if(UNIX)
enable_language(ASM)
# see if we are building 32-bit or 64-bit executables
file(WRITE ${CMAKE_BINARY_DIR}/check_32or64bit.cpp "int main(int argc,
char *argv[]) { return 8 *
Within CTK,
Where we are specifying a specific SHA1, we could set UPDATE_COMMAND to be
""
Where we are specifying a branch like "origin/master", this is were the
problem occurs. I guess we could also specify a given SHA1. This will
prevent the external project to be a moving target and will ensur
On 08/01/2011 07:13 PM, The Novice Coder wrote:
>
> The short version of what I'm trying to do:
> Add some kind of definition to the cmake file that specifies a file,
> that if modified, will cause the project to be regenerated.
>
>
> Longer (more specific) version.
> We (our small program team
On 8/2/2011 9:42 AM, David Cole wrote:
Try commenting out the one line that causes problems, then back up
from there, either commenting chunks out or adjusting CMake options
until those commands are not loaded.
That said, if CMake is built with the same options as you are building
VTK with, the
Try commenting out the one line that causes problems, then back up
from there, either commenting chunks out or adjusting CMake options
until those commands are not loaded.
On Tue, Aug 2, 2011 at 8:50 AM, John R. Cary wrote:
> Thanks for your response. This will definitely decrease my headpain.
Thanks for your response. This will definitely decrease my headpain.
It turns out that I need vtk-5.0.0, but right now I am not sure
that I need the wrapping code. Am checking on this.
Would it make sense to just not call vtkLoadCMakeExtensions.cmake?
ThxJohn Cary
On 8/2/11 5:00 AM, Davi
On Mon, Aug 1, 2011 at 5:59 PM, Sascha Zelzer
wrote:
> Hi,
>
> I played around with the ExternalProject unit tests and was able to
> reproduce my problem with the current HEAD ExternalProjects.cmake file. It
> boils down to *not* adding the UPDATE_COMMAND "" line:
>
> 1.) In CMake/Tests/ExternalPr
On Tue, Aug 2, 2011 at 7:00 AM, David Cole wrote:
> On Mon, Aug 1, 2011 at 8:34 PM, John R. Cary wrote:
>> I believe I have followed what I have found on the web for
>> building a Win64 version of CMake. I have downloaded the
>> win32 version and used it to configure the cmake source.
>> I used
On Mon, Aug 1, 2011 at 8:34 PM, John R. Cary wrote:
> I believe I have followed what I have found on the web for
> building a Win64 version of CMake. I have downloaded the
> win32 version and used it to configure the cmake source.
> I used the Visual Studio 9 2008 Win64 generator.
>
> However, wh
Hello,
Have a look there:
http://www.cmake.org/cmake/help/cmake-2-8-docs.html#command:file
especially the
file(MAKE_DIRECTORY [directory1 directory2 ...])
file command version
Regards,
Camille
De : Julien Dardenne
À : cmake@cmake.org
Envoyé le : Mardi 2 A
See source_group command
On Aug 2, 2011 12:51 PM, "Julien Dardenne"
wrote:
**
Hello,
I want to do the separation between .hpp and .inl in my Visual project.
Is there a command CMake to create sub folder in the project and organize my
files ?
Thanks
___
Hello,
I want to do the separation between .hpp and .inl in my Visual project.
Is there a command CMake to create sub folder in the project and
organize my files ?
Thanks
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
Hello,
I'm trying to understand how my C++ application can be compiled using CMake.
Actually, there is an include file (foo.h) which contains this line
boost::shared_ptr _p;
but which doesn't contain #include .
I can't see any include or source file in my application which includes
boost/shar
33 matches
Mail list logo
