[Paraview-developers] how to build a re-distributable linux plugin (.so)

[Felipe Bordeu Weldt]

I build the binaries (linux/osx/windows) of my plugin with the superbuild. Then I distribute the .so/.dylib/.dll file. The only problem is in linux because I use a recent version (ubuntu 14.04) to build it, then the binary is tied to a recent version of libc6.

Felipe  


Le 22 avr. 2015 à 20:31, Chiranjib Sur <sur.chiranjib at gmail.com> a écrit :

> Hi Utkarsh,
> Thanks for the suggestions. 
> My goal is to build my .so and use it with any binaries downloaded from paraview.org. What is the best way to generate my own .so plugin which can be used with any paraview distribution (either locally build or binary downloaded from praview.org)?
> 
> Thanks,
> Chiranjib
> 
> On Tue, Apr 14, 2015 at 11:11 PM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
> Try doing a "make install" with CMAKE_INSTALL_PREFIX set to some
> temporary location. That should strip the paths on the plugin. Note,
> however that you can only load this plugin on a build of ParaView
> built similarly i.e. it won't work on the ParaView binaries downloaded
> from paraview.org
> 
> On Tue, Apr 14, 2015 at 6:44 AM, Chiranjib Sur <sur.chiranjib at gmail.com> wrote:
> > Hi All,
> > I am trying to create a plugin with an intention to use with Paraview in any
> > machine (just by loading the .so file from Tools>Manage Plugins..).
> > To do that, I need to build the .so file without any hard link.
> >
> > Can anyone tell me how to do that ? There might be an answer from the
> > earlier mailing list archive. If so, kindly point me towards that.
> >
> > I am following the following steps :
> > 1. Download ParaView-4.3.1 (git clone..)
> > 2. Create a build directory
> > 3. Add my plugin under Examples/Plugins
> > 4. Run cmake from the build directory
> > 5. Run make for my plugin and a .so is created (e.g. : named as :
> > myplugin.so)
> >
> > This myplugin.so contains hard link to different locations linked to my
> > system/userID which I want to remove  so that the .so file become portable
> > and loaded from any machine with same level of system software.
> >
> > Thanking you in advance for the help.
> >
> > Chiranjib
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Search the list archives at:
> > http://markmail.org/search/?q=Paraview-developers
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview-developers
> >
> 
> _______________________________________________
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Search the list archives at: http://markmail.org/search/?q=Paraview-developers
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150423/e330ff41/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150423/e330ff41/attachment.sig>