[vtk-developers] Kitware VTK cygwin build
Dave Partyka
dave.partyka at kitware.com
Wed Oct 27 07:14:21 EDT 2010
Thanks for that fix David, I pushed it for now. I'll take a look at moving
that flag so it is excluded when building on cygwin with X11.
On Wed, Oct 6, 2010 at 9:53 AM, David Gobbi <david.gobbi at gmail.com> wrote:
> IIRC the cygwin target can support either, Bill would probably know.
> But you're right, the -lgdi32 might belong inside the CMakeLists.txt
> for Common and Rendering for cygwin/no-X11, instead of being
> set globally in vtkDetermineCompilerFlags.
>
> David
>
> On Wed, Oct 6, 2010 at 7:41 AM, Marco Atzeri <marco_atzeri at yahoo.it>
> wrote:
> > question is cygwin the target or just the development platform ?
> >
> > On cygwin target the standard graphical interface
> > is *NIX/X11 instead of gdi32
> >
> > Marco
> >
> > --- Mer 6/10/10, David Gobbi <david.gobbi at gmail.com> ha scritto:
> >
> >> Da: David Gobbi <david.gobbi at gmail.com>
> >> Oggetto: Re: [vtk-developers] Kitware VTK cygwin build
> >> A: "Dave Partyka" <dave.partyka at kitware.com>
> >> Cc: "VTK Developers" <vtk-developers at vtk.org>
> >> Data: Mercoledì 6 ottobre 2010, 14:58
> >> Just a comment on the cygwin
> >> dashboard, it looks like the -lgdi32 line
> >> in vtkDetermineCompilerFlags.cmake should be moved:
> >>
> >> @@ -26,16 +26,16 @@
> >> IF(WIN32)
> >> # The platform is gcc on cygwin.
> >> SET(VTK_REQUIRED_CXX_FLAGS
> >> "${VTK_REQUIRED_CXX_FLAGS} -mwin32")
> >> SET(VTK_REQUIRED_C_FLAGS
> >> "${VTK_REQUIRED_C_FLAGS} -mwin32")
> >> + LINK_LIBRARIES(-lgdi32)
> >> ENDIF(WIN32)
> >> IF(MINGW)
> >> SET(VTK_REQUIRED_CXX_FLAGS
> >> "${VTK_REQUIRED_CXX_FLAGS} -mthreads")
> >> SET(VTK_REQUIRED_C_FLAGS
> >> "${VTK_REQUIRED_C_FLAGS} -mthreads")
> >> SET(VTK_REQUIRED_EXE_LINKER_FLAGS
> >> "${VTK_REQUIRED_EXE_LINKER_FLAGS} -mthreads")
> >>
> >> SET(VTK_REQUIRED_SHARED_LINKER_FLAGS
> >> "${VTK_REQUIRED_SHARED_LINKER_FLAGS} -mthreads")
> >>
> >> SET(VTK_REQUIRED_MODULE_LINKER_FLAGS
> >> "${VTK_REQUIRED_MODULE_LINKER_FLAGS} -mthreads")
> >> - LINK_LIBRARIES(-lgdi32)
> >> ENDIF(MINGW)
> >> IF(CMAKE_SYSTEM MATCHES "SunOS.*")
> >> # Disable warnings that occur in X11 headers.
> >> IF(DART_ROOT AND BUILD_TESTING)
> >>
> >>
> >> On Wed, Sep 22, 2010 at 9:32 AM, Bill Lorensen <bill.lorensen at gmail.com
> >
> >> wrote:
> >> > I was also surprised I got those warnings. I'll keep
> >> digging.
> >> >
> >> > Bill
> >> >
> >> > On Wed, Sep 22, 2010 at 8:35 AM, Dave Partyka <
> dave.partyka at kitware.com>
> >> wrote:
> >> >> vtkUnicodeString is in vtkCommon which failed to
> >> compile thus none of the
> >> >> tests were built.
> >> >> As for the visibility warnings. Visibility is
> >> defined in Common\vtkABI.h
> >> >> though it "should" be defining the windows
> >> declspecs for Cygwin and not
> >> >> using __attribute__ visibility (Assuming we're
> >> talking about the same
> >> >> visibility). Feel free to dig deeper. Dash14 is
> >> extremely slow so I may not
> >> >> have any further information until tomorrow.
> >> >>
> >> >> On Wed, Sep 22, 2010 at 8:24 AM, Bill Lorensen
> >> <bill.lorensen at gmail.com>
> >> >> wrote:
> >> >>>
> >> >>> Dave,
> >> >>>
> >> >>> I see today that the cygwin build is getting
> >> closer. But none of the
> >> >>> tests are running.
> >> >>>
> >> >>> I am using cygwin version 1.7.7, gcc-4.3.4 and
> >> cmake 2.6-patch4.
> >> >>>
> >> >>> I build with shared libs on.
> >> >>>
> >> >>> I had to patch one file:
> >> Utilities/Cosmo/ParticleDistribute.cxx
> >> >>>
> >> >>> All built fine except that I get thousands of
> >> warnings about
> >> >>> "visibility attribute not supported in this
> >> configuration".
> >> >>>
> >> >>> All but 8 tests passed.
> >> >>>
> >> >>> I think I'll build cmake 2.8 and see if it
> >> solves the visibility issue.
> >> >>>
> >> >>> Bill
> >> >>>
> >> >>> On Tue, Sep 21, 2010 at 9:38 AM, Dave Partyka
> >> <dave.partyka at kitware.com>
> >> >>> wrote:
> >> >>> > It's there now. Are these any of the
> >> compile errors you guys were
> >> >>> > experiencing?
> >> >>> > http://www.cdash.org/CDash/viewBuildError.php?buildid=727533
> >> >>> > This cygwin is using gcc-3.4.4. I am
> >> pretty tempted to see if I can
> >> >>> > update
> >> >>> > it to at least 4.x.
> >> >>> >
> >> >>> > On Mon, Sep 20, 2010 at 5:40 PM, Dave
> >> Partyka <dave.partyka at kitware.com>
> >> >>> > wrote:
> >> >>> >>
> >> >>> >> It should be all set now. We should
> >> get some feedback on the dashboard
> >> >>> >> tomorrow.
> >> >>> >>
> >> >>> >> On Mon, Sep 20, 2010 at 5:04 PM, Dave
> >> Partyka
> >> >>> >> <dave.partyka at kitware.com>
> >> >>> >> wrote:
> >> >>> >>>
> >> >>> >>> Okay, I'll build it by hand on
> >> Dash14.
> >> >>> >>>
> >> >>> >>> On Mon, Sep 20, 2010 at 5:02 PM,
> >> Bill Lorensen
> >> >>> >>> <bill.lorensen at gmail.com>
> >> >>> >>> wrote:
> >> >>> >>>>
> >> >>> >>>> Dave,
> >> >>> >>>>
> >> >>> >>>> I think it would be good to
> >> verify that vtk cygwin builds with cmake
> >> >>> >>>> 2.8.x. I know it builds with
> >> 2.6.
> >> >>> >>>>
> >> >>> >>>> David Doria and I have been
> >> going around on this for a few weeks. He
> >> >>> >>>> has been working with a
> >> cygwin guy to resolve the issue, but their
> >> >>> >>>> solution looks complex to me.
> >> It would be good to have "the experts"
> >> >>> >>>> verify that VTK can indeed be
> >> built with cygwin and cmake 2.8.x.
> >> >>> >>>>
> >> >>> >>>> Bill
> >> >>> >>>>
> >> >>> >>>> On Mon, Sep 20, 2010 at 4:52
> >> PM, Dave Partyka
> >> >>> >>>> <dave.partyka at kitware.com>
> >> >>> >>>> wrote:
> >> >>> >>>> > Hi Bill,
> >> >>> >>>> > Dash14 used to do this
> >> build. It stopped working because we need
> >> >>> >>>> > cmake
> >> >>> >>>> > 2.8.x
> >> >>> >>>> > to drive the dashboard
> >> because only 2.8.x knows how to update git
> >> >>> >>>> > repositories. I built a
> >> cygwin 2.8.2 release binary and have been
> >> >>> >>>> > working
> >> >>> >>>> > with Bill Hoffman on
> >> getting it submitted to the cygwin package
> >> >>> >>>> > managers.
> >> >>> >>>> > Once it's done, I can
> >> update dash14 packages with their package
> >> >>> >>>> > manager.
> >> >>> >>>> > If this is critical for
> >> you I can build cmake 2.8.2 by hand on that
> >> >>> >>>> > machine.
> >> >>> >>>> > Otherwise I will wait
> >> for the cygwin guys to make the package
> >> >>> >>>> > available
> >> >>> >>>> > through their package
> >> manager.
> >> >>> >>>> >
> >> >>> >>>> > On Mon, Sep 20, 2010 at
> >> 4:45 PM, Bill Lorensen
> >> >>> >>>> > <bill.lorensen at gmail.com>
> >> >>> >>>> > wrote:
> >> >>> >>>> >>
> >> >>> >>>> >> Folks,
> >> >>> >>>> >>
> >> >>> >>>> >> At one time, kitware
> >> had a cygwin build for VTK. Can someone
> >> >>> >>>> >> revive
> >> >>> >>>> >> that? We need to
> >> verify that VTK still builds with cygwin and
> >> >>> >>>> >> cmake
> >> >>> >>>> >> 2.8.2...
> >> >>> >>>> >>
> >> >>> >>>> >> Bill
> >> >>> >>>> >>
> >> _______________________________________________
> >> >>> >>>> >> Powered by
> >> www.kitware.com
> >> >>> >>>> >>
> >> >>> >>>> >> Visit other Kitware
> >> open-source projects at
> >> >>> >>>> >> http://www.kitware.com/opensource/opensource.html
> >> >>> >>>> >>
> >> >>> >>>> >> Follow this link to
> >> subscribe/unsubscribe:
> >> >>> >>>> >> http://www.vtk.org/mailman/listinfo/vtk-developers
> >> >>> >>>> >>
> >> >>> >>>> >
> >> >>> >>>> >
> >> >>> >>>
> >> >>> >>
> >> >>> >
> >> >>> >
> >> >>
> >> >>
> >> > _______________________________________________
> >> > Powered by www.kitware.com
> >> >
> >> > Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
> >> >
> >> > Follow this link to subscribe/unsubscribe:
> >> > http://www.vtk.org/mailman/listinfo/vtk-developers
> >> >
> >> >
> >> _______________________________________________
> >> Powered by www.kitware.com
> >>
> >> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
> >>
> >> Follow this link to subscribe/unsubscribe:
> >> http://www.vtk.org/mailman/listinfo/vtk-developers
> >>
> >>
> >
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20101027/9ffb437d/attachment.html>
More information about the vtk-developers
mailing list