2013/8/12 Paul Smith :
> On Mon, 2013-08-12 at 22:35 +0200, Eric Noulard wrote:
>> 2013/8/12 Paul Smith :
>> >
>> > So I have tried using add_custom_command() with OUTPUT, but the
>> > documentation says:
>> >
>> > "Do not list the output in more than one independent target that may build
>> > in p
On Mon, 2013-08-12 at 22:35 +0200, Eric Noulard wrote:
> 2013/8/12 Paul Smith :
> >
> > So I have tried using add_custom_command() with OUTPUT, but the
> > documentation says:
> >
> > "Do not list the output in more than one independent target that may build
> > in parallel or the two instances of
2013/8/12 Paul Smith :
> Hi all.
>
> I've got a situation where I'm creating generated source files (from
> bison/flex, actually, but I'm writing my own rules for it since I need
> specialized support for C++ output, etc.)
>
> However I need to compile the generated output into two different librar
Hi all.
I've got a situation where I'm creating generated source files (from
bison/flex, actually, but I'm writing my own rules for it since I need
specialized support for C++ output, etc.)
However I need to compile the generated output into two different
libraries, building two different ways (w
I have a project where the output is a static library. The directory
structure is as follows:
myproj
| CMakeLists.txt
|- cmake_macros
|find_include_dirs.cmake
|- libs
|--- Mac
|- lib
| libcrypto.a
| ...
|--- win
| ...
|
|- src
|--- co
Hi,
I am afraid you will have to write a new generator for cpack. It is not as
hard as it sound but you will have to write C++ code. That would be great
if cpack could support inno setup since it is much easier to hack inno
setup script than NSIS script.
Cheers,
-Nico
On Monday, August 12, 201
Hi folks,
(hope this post does not double up with an existing one ; I tried to check
past posts in the archives but did not find any)
I have this existing project on Windows (only) that require some automatic
packaging - the current procedure is a painful doc to read and follow with
multiple step
