[omniORB] building omniORBpy

[Kevin Wooten]

omniORBpy is built using the BOA of omniORB itself, so they are inherantly somewhat codependant. I believe most fixes for omniORB are going to require a rebuild of omniORBpy, unless the fix is restricted to the omniORB POA itself.

>> -----Original Message-----
>> From: Arnault Bonafos [mailto:arnault.bonafos@tumbleweed.com]
>> Sent: Wednesday, July 24, 2002 12:46 PM
>> To: 'omniorb-list@realvnc.com'
>> Subject: [omniORB] building omniORBpy
>> 
>> 
>> Hello,
>> I have a simple question regarding omniORBpy 2.0-beta2, that 
>> I downloaded
>> yesturday, and the versioning strategy.
>> 
>> The release notes of omniORBpy says that the archive should 
>> be expanded into
>> the src/lib directory of the omniORB source tree and we are 
>> wondering if
>> there is a way to have completely two different trees for 
>> omniORBpy and
>> omniORB so that can minimize dependancies between the two.
>> Also we were wondering how omniORBpy developers were 
>> handling versions
>> during the development, basically src/lib/omniORBpy is tagged
>> "omnipy2_develop", which tag is used for dependent libraries in bin
>> (omniORB400_rt.dll and omnithread30_rt.dll)?
>> 
>> Also in the case of one source directory how will be handled 
>> versioning in
>> the futur?
>> For example let's imagine that a fix goes into one of the 
>> public templates
>> of omniORB, will it require a recompilation of omniORBpy?
>> 
>> Arnault.
>> --
>> 
>> Arnault Bonafos	               SE II
>> Tumbleweed    Communications    Corp.
>> ph: (650) 216-2027  fx: (650) 216-2003
>> 
>> 
>> _______________________________________________
>> omniORB-list mailing list
>> omniORB-list@realvnc.com
>> http://www.realvnc.com/mailman/listinfo/omniorb-list
>>