Hi Alan
The I've had a look and it seems that there are two problems. I'm not
sure if these are CMake version issues as much as anything else.

Basically in the foreach on line 4 of concatenate_pkgIndex.tcl.cmake
the filenames need quoting. However, even when this is done, my
version of CMake complains that the variables are split with a
semicolon rather than a space, so the semicolon separator needs
replacing with a space too. Knowing that in the foreach a space should
be used rather than a semicolon makes the cause of the problem clear.

So I can see where the lines appear to be written from the
CMakeLists.txt, but I don't know how to split that block to output the
individual ${index} list items. I might have to rely on you to have a
look.

Phil

On 14 June 2015 at 17:36, Alan W. Irwin <ir...@beluga.phys.uvic.ca> wrote:
> On 2015-06-14 11:12+0100 Phil Rosenberg wrote:
>
>> I've recently started getting a build error for TCL
>>
>> The error I get is
>>
>> 8>------ Build started: Project: concatenate_pkgIndex.tcl,
>> Configuration: Release x64 ------
>> 8> Building Custom Rule
>> D:/usr/local/src/plplot-plplot/bindings/CMakeLists.txt
>> 8> CMake does not need to re-run because
>> D:\usr\local\src\plplot-plplot\build\Visual Studio 11
>> 64s\bindings\CMakeFiles\generate.stamp is up-to-date.
>> 8> Generating pkgIndex.tcl
>> 8> CMake Error at concatenate_pkgIndex.tcl.cmake:4 (file):
>> 8> file failed to open for reading (No such file or directory):
>> 8>
>> 8> D:/usr/local/src/plplot-plplot/build/Visual Studio 11
>> 64s/bindings/Studio
>> 8>
>> 8>
>>
>> Looking at the path it is trying to find I would guess that the issue
>> is related to me having spaces in my build path.
>>
>> Unfortunately this error means that my INSTALL project (the equivalent
>> to make install) doesn't run to completion and I am currently having
>> to manually copy the built results to the install directory.
>
>
> Hi Phil:
>
> You can use
>
> git blame bindings/CMakeLists.txt |less
>
> to discover the last change in this concatanation logic was done by me
> on 2015-04-21.  And you can then use
>
> git blame a8873275^ bindings/CMakeLists.txt |less
>
> to show the previous change to the concatanation part of the code was back
> in 2009-11-01 so likely not
> relevant to the issue you just discovered.
>
> I have also used
>
> git diff a8873275^..a8873275 bindings/CMakeLists.txt |less
>
> to look carefully at the change in logic there which simply changes
> the contatanation from cmake time to build time.  I frankly don't see
> how that change affects "spaced" path issues so perhaps using
> the cmake -P command to exercise this logic at build time somehow
> treats blanks in pathnames differently than the original logic?
>
> Anyhow, to investigate further, will you please take a look at the
> file bindings/concatenate_pkgIndex.tcl.cmake in the build tree which
> is generated at CMake time by the CMake concatanation logic in
> bindings/CMakeLists.txt and executed at run time by building the
> concatenate_pkgIndex.tcl target which in turn simply runs
>
> cmake -P bindings/concatenate_pkgIndex.tcl.cmake
>
> You can also run that command by hand to see exactly what the issue is.
>
> If there is some obvious part of that generated file that needs quotes
> around the pathname, please insert the corresponding escaped quotes
> into the concatanation logic in bindings/CMakeLists.txt, test that
> change, and if it works for you please push it.
>
> Alan
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________

------------------------------------------------------------------------------
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to