On Jan 29 2014 3:44 PM, John Morris wrote:
> On 01/21/2014 10:23 AM, EBo wrote:
>> On Jan 21 2014 8:10 AM, Sebastian Kuzminsky wrote:
>>> On 01/21/2014 03:00 AM, EBo wrote:
>>>> I had a few minutes so I thought I would take a poke at getting
>>>> LinuxCNC to run on Gentoo again. To help manage any spluge, I
>>>> typically
>>>> install experimental projects in their own /opt tree. When
>>>> installing
>>>> linuxcnc in /opt, it cannot find a whole raft of stuff (starting
>>>> with
>>>> the wizard gif). I can probably hack around this, BUT it would be
>>>> nice
>>>> if UBC and 2.6.0 as a whole respected the ${PREFIX} and ${DEST}
>>>> directives.
>>>
>>> configure calls it ${prefix}, and you can set it with (for example)
>>> "configure --prefix=/opt". Also, maybe instead of DEST you can use
>>> the
>>> DESTDIR environment variable, which we also support?
>>>
>>> I'd guess if you set --prexfix to /opt and don't use DESTDIR, it
>>> might
>>> work. But you're definitely breaking new ground here, so expect a
>>> bit
>>> of a rough ride.
>>
>> Yes, I was referring to --prefix=/opt/linuxcnc. I got master to
>> work
>> after a fashion, but I see that there were a number of places that
>> still
>> looked in the code to be installed in /usr/share instead of
>> /opt/linuxcnc/share, but I could be wrong there. There are other
>> places
>> where the parts are expected to be installed in a relative order
>> (which
>> is one of the reasons I put it in /opt/linuxcnc, so it will not
>> interfere/conflict with the distribution's standard locations).
>
> Hi EBo,
>
> I went through quite a lot of the build system while working on UBC3
> to
> fix this kind of problem, partly to clean up the confusing
> {C,LD}FLAGS-like variables that had over time sprouted in so many
> nooks
> and crannies, partly for portability to Red Hat-derivatives, and of
> course partly to deal with the more modular 'Unified Build'. I
> haven't
> tried setting ${prefix} to /opt, but will when I get some time. If
> something's breaking, it's either something I haven't fixed, or else
> something I broke. :)
>
> You've hit on a topic I've been moaning about ever since the work on
> the
> UBC3 build system and run-time scripts, but haven't yet written out a
> full statement of the problem. It seems that once upon a time there
> was
> a pre-autoconf build system that centered around $EMC_HOME. At some
> point, autoconf was added, and ${prefix} and other autoconf variables
> were adopted for non-RIP system installs. The result is pretty
> fragile,
> and I keep finding paths that haven't been converted to autoconf.
>
> When I get around to it, I'll make an argument to merge RIP builds
> and
> system installs; in this case, RIP builds would be like system
> installs,
> but with ${prefix} perhaps set to the top level of the source tree.
> That will help prevent divergence between RIP and system builds, and
> make it much more likely that a less-commonly used prefix like
> /opt/linuxcnc would operate as it should.
One addition aldvantage would be a consistent install path. If the UB
did a pre-install of everything in the LCNC tree, then they would be the
same -- ie:
${SOURCE}/build/bin
lib
share
doc
...
or some such, then the LINUCCNC_HOME would have a consistent meaning.
Also, I think we should take the opportunity to remove the EMC
reference...
EBo --
...
------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends. Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
