[CMake] Copying cmake generated files to another machine

Pau Garcia i Quiles pgquiles at elpauer.org
Mon Dec 7 16:42:47 EST 2009


On Mon, Dec 7, 2009 at 10:36 PM, Óscar Fuentes <ofv at wanadoo.es> wrote:
> steve naroff <snaroff at apple.com> writes:
>
>> Our current thinking is to post process the cmake generated files and
>> remove all the absolute paths (since the project files are simply
>> text). Since cmake is a black box to me (and I am unfamiliar with it's
>> generated 'code'), it's unclear if this a 'good' idea? Or will I bump
>> into other gotcha's?
>
> I suggested that option to you on the past.
>
> My guess is that the VS project files generated by CMake depends less on
> absolute paths than the Makefiles generated for other build
> systems. Building in-source maybe diminishes the amount of work too.
>
> As LLVM/clang have no external dependencies, the problem is simpler. If
> VS is installed on C: and the LLVM source and build directories are on
> C: too, the problem is even simpler, because you can always replace an
> absolute path with a relative one.
>
> My advice is to start small: with a text editor, edit the top-level
> project file, then edit the project file of lib/System, which does not
> depend on any other file. Move the whole tree to somewhere else, open VS
> and build just the System library. If it works, that's good. Proceed to
> write a script for automating the absolute->relative path conversion.

You are wasting your time.

It's not going to be that easy. You will need to replace all the calls
to CMake with generated stuff. Even in the improbable case you
succeed, you would be giving people something which somewhat works,
you would not be shipping the actual buildsystem but some kind of a
pseudo-pre-geneated buildsystem.

Morale: anal retentive people must learn that opening your ass to
something new may make you happier.

-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)


More information about the CMake mailing list