Sorry, I haven't been diligent about following the list.
On 01/20/2014 02:32 AM, Michael Haberler wrote:
>
> Am 20.01.2014 um 09:23 schrieb Sebastian Kuzminsky <[email protected]>:
>
>> Reporting ubc issues to the list as requested.
>>
>> The ubc build system creates symlinks to "." in src/rtapi/${flavor}/, is
>> that intentional?
>
> yes it is; John has the full debrief on this
>
> as others have discovered before us, kbuild does force some awkwardness
Kbuild is the source of the weirdness in src/objects/*-kernel, where the
src tree must be duplicated to keep kbuild from stomping on itself when
building the same source files for different flavors.
Below is what I wrote in src/rtapi/Submakefile. In this case, the
problem is that macros within a particular source file may change
between flavors, but as it says below, TOOBJS doesn't know how to build
the same source file into a different location.
##########################################
# Separate sources hack
#
# ulapi.so needs sources to be built separately for each flavor. The
# Makefile rules, and TOOBJS & friends, always build the same source
# file into the same object file.
#
# Hack around this by creating a symlink 'rtapi/<flavor>' that points
# back to the rtapi directory. Then the same source can be referred
# to as 'rtapi/<flavor1>/foo.c' or 'rtapi/<flavor2>/foo.c', and thus
# be built into separate object files.
John
PS: I'm sure it will cause horror and consternation just to mention,
but a year ago I wrote about 80% of a cmake build system for the
LinuxCNC core. It's like a breath of fresh air to anyone who's spent
more than a few days wrestling with the current system.
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
