On Mon, Apr 23, 2012 at 8:38 AM, Andrea Crotti wrote:
> On 04/23/2012 01:32 PM, David Cole wrote:
>
>> You should just get used to using shorter paths on the embarrassing OS.
>>
>> This is an early warning sign for you that your end users will also
>> encounter these problems as they install your
On 04/23/2012 01:32 PM, David Cole wrote:
You should just get used to using shorter paths on the embarrassing OS.
This is an early warning sign for you that your end users will also
encounter these problems as they install your program on their systems
in "non-short" root paths...
You can ig
You should just get used to using shorter paths on the embarrassing OS.
This is an early warning sign for you that your end users will also
encounter these problems as they install your program on their systems in
"non-short" root paths...
You can ignore it if you wish, but the fact remains that
On 04/20/2012 12:36 PM, Eric Noulard wrote:
Nope, it would break backward compatibility, you can dig the ML
for discussion about that "issue".
My opinion is that building in-source is a bad habit that ought to be
discouraged but the fact is,
this is not currently easy to enforce out-of-source:
h
2012/4/20 Andrea Crotti :
> On 04/19/2012 07:00 PM, Eric Noulard wrote:
>>
>> Compiler, Visual Studio something?
>> You run cpack from the command line or from within IDE/Makefile etc
>>
>
> No compilers used for this project (it's python) and I run from command
> line.
>
> Anyway it might be a
On 04/19/2012 07:00 PM, Eric Noulard wrote:
Compiler, Visual Studio something?
You run cpack from the command line or from within IDE/Makefile etc
No compilers used for this project (it's python) and I run from command
line.
Anyway it might be a good idea also in general so I tried to d
2012/4/19 Andrea Crotti :
> On 04/19/2012 04:13 PM, Eric Noulard wrote:
>>
>> Could you build out-of-source in a small path?
>> like
>>
>> small/path/build
>> when your source would be in
>> long/path/source
>>
>> cpack should only work with file in the build tree.
>>
>> this is a workaround but it
On 04/19/2012 04:13 PM, Eric Noulard wrote:
Could you build out-of-source in a small path?
like
small/path/build
when your source would be in
long/path/source
cpack should only work with file in the build tree.
this is a workaround but it may work.
By the way:
Which version of CMake/CPack
2012/4/19 Andrea Crotti :
> We are trying to make cmake work with our projects, and all the targets work
> fine.
>
> The problem is that on some projects cpack -G NSIS fails because when it
> tries to copy
> files around it generates paths too long.
>
> I found that CMake is able to handle these si
We are trying to make cmake work with our projects, and all the targets
work fine.
The problem is that on some projects cpack -G NSIS fails because when it
tries to copy
files around it generates paths too long.
I found that CMake is able to handle these situations in theory with a
checksum
10 matches
Mail list logo
