Hi,
Another example along Kenneth's lines:
https://github.com/gromacs/gromacs/blob/master/docs/manual/CMakeLists.txt
Mark
On Mon, Jan 12, 2015 at 5:10 PM, Moreland, Kenneth
wrote:
> Unlike Myles' answer, I'm going to assume that by noticing *.m files have
> changed you mean that the changes ar
On 10/01/15 14:01, Gonzalo Garramuño wrote:
I have created an NSIS section for my CMakeLists.txt and I am trying
to pack and install my application (mrViewer).
I managed to make it all work by flattening the destination, so that
instead of ${mrViewerPackageName}/bin, it remains as bin only.
Al
That's it
I changed to C++ compiler to g++ and re-generated the project and it build
and linked. Thanks a lot.
Robert Ramey
--
View this message in context:
http://cmake.3232098.n2.nabble.com/linking-gcc-on-osx-tp7589456p7589457.html
Sent from the CMake mailing list archive at Nabble.co
I use my Mac OSX to test my code against gcc 4.8. I've installed the
appropriate command line tools and the compiler/linker works fine from the
command line.
My CMakeLists.txt project file works fine to generate an Xcode project for
build and test. I can also use it to generate a makefile projec
Hi Chris,
> One of my co-workers likes to start multiple makes in various parts of his
> project source tree. Under our old Makefile-based, build-in-source system,
> this worked fine. Under our new CMake-based, out-of-source build system, this
> causes problems, since any make might cause CMak
Hi Robert,
Regarding your questions:
1) You should use the following CTEST_DROP_LOCATION:
set(CTEST_DROP_LOCATION "/submit.php?project=Safe+Numerics")
2) For the free version of hosted cdash, the builds are deleted every 30
days. That's why you will not be able to see the builds submitted 2
Unlike Myles' answer, I'm going to assume that by noticing *.m files have
changed you mean that the changes are picked up when a make build is run,
not necessarily using a daemon to pick up exactly when the change occurs.
You should be able to set a trail of dependencies for make to pick up the
ch
Hi Nils,
On Mon, Jan 12, 2015 at 11:50 AM, Nils Gladitz
wrote:
> On 01/12/2015 11:40 AM, Andreas Pakulat wrote:
>
>> Ah, that works. Its a little ugly in the CMake files but I guess I can
>> live with that. Ideally I was hoping to simply have a 'complete' list
>> including actual sources and sou
Hello Rob,
Rob McDonald writes:
> I am familiar with UseLATEX, but would like to take the automation of
> my document build system a step or two further. Solutions that build
> on UseLATEX -- or a totally separate approach, are OK.
>
> I often use Matlab to create *.pdf figures -- which are the
On 01/12/2015 11:40 AM, Andreas Pakulat wrote:
Ah, that works. Its a little ugly in the CMake files but I guess I can
live with that. Ideally I was hoping to simply have a 'complete' list
including actual sources and sources for other platforms and hand that
to a special function - without passin
Hi,
On Sun, Jan 11, 2015 at 10:55 PM, Dario Oliveri
wrote:
> It is very simple for each of the files you want to include in the build
> (I use txt example so that you know it can work for arbitrary types):
>
> ---
> set_source_files_properties( comment.txt PROPERTIES HEADER_FILE_ONLY true)
> ---
11 matches
Mail list logo