[omniORB] omniORB cross-compilation issue
Vyacheslav.Yurkov at bruker.com
Wed Dec 6 12:34:44 GMT 2017
I produce several builds: target, native and nativesdk. Nativesdk build actually contains omniidl. It's intended for developers and supposed to run on the other developer's machine, neither compile host, nor the target (although operating system matches compile host).
From: Duncan Grisby [mailto:duncan at grisby.org]
Sent: Mittwoch, 6. Dezember 2017 13:24
To: Yurkov, Vyacheslav; omniorb-list at omniorb-support.com
Subject: Re: [omniORB] omniORB cross-compilation issue
On Wed, 2017-11-29 at 09:45 +0000, Yurkov, Vyacheslav via omniORB-list
> I use omniORB in our Yocto Linux based SDK. Unfortunately omniidl
> script is wrong after cross-compilation. When cross-compilation is
> done @PYTHON@ variable is replaced with an absolute path to python in
> sysroot location, which is wrong, because that path won’t be
> available when SDK is installed. I came up with a patch (attached)
> fixing that.
How are you cross compiling it? In a cross-compilation, it should not
build omniidl at all, because omniidl needs to run on the compile host,
not on the target system.
-- Duncan Grisby --
-- duncan at grisby.org --
-- http://www.grisby.org --
More information about the omniORB-list