Re: [cmake-developers] CPack/NSIS is broken after extended length paths fix

2015-09-21 Thread Clinton Stimpson
On Monday, September 21, 2015 12:28:37 PM Dmitry Kochkin wrote: > Hi Clint, > > >>Actually it's even worse because in current master HEAD I can see that > >>INST_DIR is empty in generated project: !define INST_DIR "" > >>(not sure if that's caused by your change) > > > >Interesting... Do you

Re: [cmake-developers] CPack/NSIS is broken after extended length paths fix

2015-09-21 Thread Dmitry Kochkin
Hi Clint, >>Actually it's even worse because in current master HEAD I can see that >>INST_DIR is empty in generated project: >>  !define INST_DIR "" >>(not sure if that's caused by your change) >Interesting... Do you know why this happens?  How is this problem related to >extended paths (with

[cmake-developers] CPack/NSIS is broken after extended length paths fix

2015-09-18 Thread Dmitry Kochkin
Hi Clinton, I was looking into an issue that we have in CMake on Windows with extended paths and later on realized that you've fixed it. However I've realized that you fixed it only in cmSystemTools, which fixes e.g. INSTALL, but does not fix cpack. Actually it's even worse because in current

Re: [cmake-developers] CPack/NSIS is broken after extended length paths fix

2015-09-18 Thread clinton
- On Sep 18, 2015, at 6:07 AM, Dmitry Kochkin wrote: > Hi Clinton, > I was looking into an issue that we have in CMake on Windows with extended > paths > and later on realized that you've fixed it. > However I've realized that you fixed it only in cmSystemTools, which fixes