Re: [xml-cppdom-devel] Building cppdom prefix problem

[Patrick H. <pa...@13...>]

Doug McCorkle wrote:
> On Feb 15, 2007, at 3:58 PM, Patrick Hartling wrote:
>=20
>> Doug McCorkle wrote:
>>> Hello,
>>>      Currently, when building cppdom, headers and libs are installed
>>> in prefix even if the install target is not listed. This causes
>>> issues when trying to make cppdom accessible through MacPorts. In
>>> general this seems to be somewhat of a problem.
>> That sounds like bad behavior in general. Software shouldn't be =20
>> installing
>> itself unless told to do so.
>>
>> The CppDOM build is in pretty bad shape and hasn't ever been quite =20
>> what I
>> would call ideal. The installation part has never really worked =20
>> correctly,
>> but I don't think I have seen this specific behavior. What I have =20
>> seen is
>> that running the build separately from the installation doesn't =20
>> work well,
>> but the build certainly should support a two-step build+install =20
>> process.
>> What version are you using?
>>
> 0.6.6 source I believe.

OK. I suspect that the current 0.7 code is broken similarly, but I haven'=
t
checked.

>>> I "fixed" the problem
>>> by adding guards in the scons files but that may not be the solution
>>> everyone is looking for. Thoughts?
>> What are guards in this context?
>=20
> if 'install' in COMMAND_LINE_TARGETS:

Yikes. I am surprised that the build behaves this way, and yet, I bet it'=
s
because of the "developer" installation aspect. I am pretty sure that the=

CppDOM build performs an installation after building so that developers
don't have to run the separate install step (such a burden!). Perhaps wha=
t
needs to happen is that the build needs to look at the prefix setting and=

only perform the automatic installation-after-build step if the prefix is=

the developer installation.

 -Patrick


--=20
Patrick L. Hartling                    | VP Engineering, Infiscape Corp.
PGP: http://tinyurl.com/2oum9          | http://www.infiscape.com/