[prev in list] [next in list] [prev in thread] [next in thread] 

List:       omniorb-list
Subject:    Re: [omniORB] omniORB cross-compilation issue
From:       Duncan Grisby via omniORB-list <omniorb-list () omniorb-support ! com>
Date:       2017-12-06 13:39:56
Message-ID: 1512567596.28838.4.camel () grisby ! org
[Download RAW message or body]

On Wed, 2017-12-06 at 12:34 +0000, Yurkov, Vyacheslav wrote:

> 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).

OK. That is not the normal case for cross-compilation, but if it works
for you then it's a reasonable thing to do.

Considering what you are doing, I can see why you want to use
#!/usr/bin/env python in the omniidl script. However, that can't be
done in the core distribution because it would break for any user who
uses a python executable that is not the first one in the PATH.

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan@grisby.org     --
   -- http://www.grisby.org --


_______________________________________________
omniORB-list mailing list
omniORB-list@omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list
[prev in list] [next in list] [prev in thread] [next in thread]