[omniORB] Compiling
David Newcomb
david.newcomb at bigsoft.co.uk
Mon Jan 17 13:54:18 GMT 2011
Ok, we are cooking on gas now!
Compiled up the omniORB-4.1.5 and omniORBpy-3.5 against Python 2.7.1 and
everything seems to have worked.
Is there another command I can run which produces the installable exe of
this module (e.g. omniorbpy-3.5.win32-py2.7.exe) for distribution?
Many thanks,
David.
On 14 January 2011 17:55, David Newcomb <david.newcomb at bigsoft.co.uk> wrote:
>
> Followed the instructions in the README.win32.txt and kicked of a build.
> Both CPUs are at 50% but the compile has now been running for 18 hours which
> I don't think is normal. The only output was this:
>
> # =================
> $ make export
> making export in src/lib/omniORBpy/modules...
> make[1]: Entering directory
> `/cygdrive/c/python-modules/omniORB-4.1.4-x86_win32-vs9/src/lib/omniORBpy/modules'
> + install -c pydistdate.hh ../../../../include/omniORB4
> # =================
>
> The omniORB distribution I have downloaded contains the binaries, so do I
> take it from Duncan's post that I have to do a clean build anyway? I think
> that I'll start again on Monday and let you know how that goes.
>
> Regards,
> David
>
>
>
> On 14 January 2011 17:04, Duncan Grisby <duncan at grisby.org> wrote:
>
>> On Tue, 2011-01-11 at 12:39 +0000, David Newcomb wrote:
>>
>> > I am trying to build omniORBpy against VC9 and Python 2.7 and have run
>> > into a couple of issues.
>> >
>> > I chose the latest version of omniORBpy-3.5.
>> > omniORB-4.1.5 doesn't have a win32 vc9 version so I'm using
>> > omniORB-4.1.4-x86_win32-vs9(.zip). The README says that everything is
>> > pre-built so not much to do there (hurray).
>>
>> Although it will probably work to build omniORBpy 3.5 against omniORB
>> 4.1.4, it is not how it is meant to be used, and nobody has tested it.
>> You should use omniORB 4.1.5.
>>
>> You need to build omniORB yourself.
>>
>> > The README in omniORBpy says to place the omniORBpy-3.5 folder into
>> > omniORB-4.1.4-x86_win32-vs9/src/lib/omniORBpy ($TOP/src/lib) and
>> > change to that folder ($TOP/src/lib/omniORBpy) and do a make export.
>> >
>> > Firstly, there is no make command so I used nmake, second there is no
>> > makefile so I had to use the -f option and thirdly, the thing didn't
>> > seem to like it anyway.
>>
>> You need to use Cygwin and GNU make. Look at the instructions in
>> README.win32.txt in the omniORB tree.
>>
>> Cheers,
>>
>> Duncan.
>>
>> --
>> -- Duncan Grisby --
>> -- duncan at grisby.org --
>> -- http://www.grisby.org --
>>
>>
>>
>
--
Managing Director
BigSoft Limited
Reading, UK.
+44 (0) 7866 262 398
http://www.bigsoft.co.uk/
Registered in Cardiff, Wales 3960621
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20110117/4de6b875/attachment.htm
More information about the omniORB-list
mailing list