From: Wheeler, F. W (GE G. Research) <wh...@ge...> - 2011-01-30 17:02:48
|
I notice that v3p/j2k builds shared libraries by default. Will those libs work if they are static? If so I would vote for having them static by default with an option for shared. I'm not against shared libraries, but since everything else in VXL is static, these new shared libs now add a requirement that projects that use VXL get paths set to find the shared libs. Fred Wheeler |
From: Wheeler, F. W (GE G. Research) <wh...@ge...> - 2011-01-31 11:30:12
|
Thanks Peter. I guess what I should have said is that the v3k/j2k should be shared/static depending on BUILD_SHARED_LIBS. Right now they are always shared. Fred > -----Original Message----- > From: Peter Vanroose [mailto:pet...@ya...] > Sent: Sunday, January 30, 2011 6:04 PM > To: Wheeler, Frederick W (GE Global Research) > Cc: vxl...@li... > Subject: Re: v3p/j2k shared libs > > Actually, I have been building vxl with shared libs since quite some time, > without much problems. > > Just set > BUILD_SHARED_LIBS:BOOL=ON > in your CMakeCache.txt > > There should be no "default" choice enforced: both static and shared should > build & work correctly. > > -- Peter. > > > > Wheeler, Frederick W <wh...@ge...> wrote: > > I notice that v3p/j2k builds shared libraries by default. Will those > > libs work if they are static? If so I would vote for having them static > > by default with an option for shared. I'm not against shared libraries, > > but since everything else in VXL is static, these new shared libs now > > add a requirement that projects that use VXL get paths set to find the > > shared libs. > > > > Fred Wheeler > > > > > > > > |
From: Peter V. <pet...@ya...> - 2011-01-31 21:52:15
|
Actually, the main reason why I responded is because I'm using shared libs, which causes build failures in bil_algo and in some of the subdirs of contrib/brl/bseg/boxm2 Reason: cyclic dependencies. Did no-one else encounter that problem? (E.g.: bil_algo depends on sdet and vice versa.) -- Peter. |