Hi Michael,
> They look like they need to be forwarded upstream, but should not hold up
> an upload.
The spelling error needs to be forwarded.
Since I had to touch the package anyway, I now corrected the other two.
> - I'd target "experimental" not unstable (solely for not causing problems
> wi
Hi Gert,
On Fri, Jan 16, 2015 at 10:39 AM, Michael Hanke
wrote:
> I am currently building the package, and if that shows no problems, I will
> upload after a bit of testing. Few more things:
>
> - I'd target "experimental" not unstable (solely for not causing problems
> with the stable release)
Hi Gert,
On Thu, Jan 15, 2015 at 5:12 PM, Gert Wollny wrote:
> Hello,
>
> I've now upload the latest changes, with that the package should be okay
> for upload.
>
> Additional changes:
>
> * eliminated lintian warning: menu-icon-uses-relative-path
> * added watch file
> * corrected dependenci
Hello,
I've now upload the latest changes, with that the package should be okay
for upload.
Additional changes:
* eliminated lintian warning: menu-icon-uses-relative-path
* added watch file
* corrected dependencies
* builds in sid pbuilder amd64
There are still some lintian info mes
Hi Gert,
On Jan 14, 2015 5:08 PM, "Gert Wollny" wrote:
>
> Hello all,
>
> now that Paul provided an official upstream tarball I took the liberty
> to update the itksnap package to version 3.2.0 in the packaging git on
> alioth. There is still a lintian warning about
>
> menu-icon-uses-relativ
Hello all,
now that Paul provided an official upstream tarball I took the liberty
to update the itksnap package to version 3.2.0 in the packaging git on
alioth. There is still a lintian warning about
menu-icon-uses-relative-path
and some warnings about NMU, because currently my name is i
I just pushed a commit in the dev32 branch that includes a CMAKE
flag SNAP_PACKAGE_QT_PLUGINS. Setting this to off should disable the search
for plugins.
Thanks!
Paul
On Thu, Oct 23, 2014 at 12:27 PM, Paul Yushkevich wrote:
> Oh... Weird. Could you try without the space after -D?
>
> Thanks!
>
Oh... Weird. Could you try without the space after -D?
Thanks!
On Thu, Oct 23, 2014 at 12:05 PM, Michael Hanke wrote:
> Hi,
>
> On Thu, Oct 23, 2014 at 11:57:19AM -0400, Paul Yushkevich wrote:
> > Hi Michael,
> >
> > I am confused :)
> >
> > You previously mentioned that the file
> > /usr/lib/x
Hi,
On Thu, Oct 23, 2014 at 11:57:19AM -0400, Paul Yushkevich wrote:
> Hi Michael,
>
> I am confused :)
>
> You previously mentioned that the file
> /usr/lib/x86_64-linux-gnu/cmake/Qt5/Qt5Config.cmake
> exists on the system
>
> I was suggesting to set the prefix path to /usr/lib/x86_64-linux-gn
Hi Michael,
I am confused :)
You previously mentioned that the file
/usr/lib/x86_64-linux-gnu/cmake/Qt5/Qt5Config.cmake
exists on the system
I was suggesting to set the prefix path to /usr/lib/x86_64-linux-gnu/cmake
- so that directory should exist
I am happy to add a CMake flag that will disab
On Thu, Oct 23, 2014 at 11:26:50AM -0400, Paul Yushkevich wrote:
> Please try cmake ... -D CMAKE_PREFIX_PATH:STRING=/usr/lib/
> x86_64-linux-gnu/cmake
>
> And let me know if that works any better.
No, it doesn't -- such a directory doesn't exist.
I believe the CMake setup assumes a rigidity of a
Michael
Please try cmake ... -D CMAKE_PREFIX_PATH:STRING=/usr/lib/
x86_64-linux-gnu/cmake
And let me know if that works any better.
Thanks!
Paul
On Thu, Oct 23, 2014 at 10:50 AM, Michael Hanke wrote:
> On Thu, Oct 23, 2014 at 10:43:56AM -0400, Paul Yushkevich wrote:
> > I am not quite sure wh
On Thu, 2014-10-23 at 16:50 +0200, Michael Hanke wrote:
> On Thu, Oct 23, 2014 at 10:43:56AM -0400, Paul Yushkevich wrote:
> The file is here:
>
> /usr/lib/x86_64-linux-gnu/cmake/Qt5/Qt5Config.cmake
I'd like to chime in that
grep -R QXcb *
in the according directory does not yield any re
On Thu, Oct 23, 2014 at 10:43:56AM -0400, Paul Yushkevich wrote:
> I am not quite sure where on the Debian system Qt cmake files are, but I
> think you should be able to find them using
>
> locate Qt5Config.cmake
The file is here:
/usr/lib/x86_64-linux-gnu/cmake/Qt5/Qt5Config.cmake
> On Thu, Oc
I am not quite sure where on the Debian system Qt cmake files are, but I
think you should be able to find them using
locate Qt5Config.cmake
Thanks!
Paul
On Thu, Oct 23, 2014 at 10:43 AM, Paul Yushkevich wrote:
> Hi Michael,
>
> Please try setting the CMAKE_PREFIX_PATH to
> [PATH_TO_QT_INSTALLA
Hi Michael,
Please try setting the CMAKE_PREFIX_PATH to
[PATH_TO_QT_INSTALLATION]/lib/cmake
In my case that's /opt/Qt/5.3/gcc_64/lib/cmake
This can be provided to Cmake with the -D command, or set in the
environment.
Please let me know if that helps
Thanks!
paul
On Thu, Oct 23, 2014 at 10:22
Hi,
On Tue, Oct 21, 2014 at 08:42:50AM -0400, Paul Yushkevich wrote:
> That's great to hear! As far as the CMAKE_PREFIX_PATH, I set it to
> /opt/Qt/5.3/gcc_64/lib/cmake. In my case, Qt is installed to /opt/Qt. I am
> not quite sure why the VTK and GDCM are becoming an issue in the debian
> build,
Hi Gert,
That's great to hear! As far as the CMAKE_PREFIX_PATH, I set it to
/opt/Qt/5.3/gcc_64/lib/cmake. In my case, Qt is installed to /opt/Qt. I am
not quite sure why the VTK and GDCM are becoming an issue in the debian
build, perhaps ITK and VTK are configured slightly differently from the way
On Tue, 2014-10-21 at 07:49 -0400, Paul Yushkevich wrote:
> Ok - it was an easy fix. I just checked it into dev32. Gert - could you
> please confirm that the code runs and builds now?
Okay, when I can build it with the patches applied (disabling the search
for the plug-ins with cmake and added VTK
On Tue, 2014-10-21 at 07:49 -0400, Paul Yushkevich wrote:
> Ok - it was an easy fix. I just checked it into dev32. Gert - could you
> please confirm that the code runs and builds now?
I still have the problems with cmake not finding the Plugins. What did
you set CMAKE_PREFIX_PATH to - I tried "/us
Ok - it was an easy fix. I just checked it into dev32. Gert - could you
please confirm that the code runs and builds now?
Thanks!
Paul
On Tue, Oct 21, 2014 at 6:58 AM, Paul Yushkevich
wrote:
> I'm getting the same error in QCoreApplication... Oddly, this happens in
> Debian but not other OSs.
>
I'm getting the same error in QCoreApplication... Oddly, this happens in
Debian but not other OSs.
Hope I can find a fix :)
On Tue, Oct 21, 2014 at 6:38 AM, Gert Wollny wrote:
> On Tue, 2014-10-21 at 06:31 -0400, Paul Yushkevich wrote:
> > A quick question about the plugins: when you build with
On Tue, 2014-10-21 at 06:31 -0400, Paul Yushkevich wrote:
> A quick question about the plugins: when you build with Cmake, did you have
> CMAKE_PREFIX_PATH set to point to the Qt5's lib/cmake directory? I think
> this is the way the plugins get picked up.
No, I didn't.
signature.asc
Descripti
Thanks, Gert,
A quick question about the plugins: when you build with Cmake, did you have
CMAKE_PREFIX_PATH set to point to the Qt5's lib/cmake directory? I think
this is the way the plugins get picked up.
I've set up a VM with Debian and am trying to build everything now.
Paul
On Tue, Oct 21,
Hello Paul,
On Tue, 2014-10-21 at 04:45 -0400, Paul Yushkevich wrote:
> I am going to try looking into this problem this week. I have been building
> on Centos, and there the Qt plugins are being picked up just fine. I
> suspect the crash is due to the missing plugin, but I am not sure.
The cra
Hi Gert,
I am going to try looking into this problem this week. I have been building
on Centos, and there the Qt plugins are being picked up just fine. I
suspect the crash is due to the missing plugin, but I am not sure.
Could you tell me why including all VTK libs and GDCM libs was required?
Th
Hello Paul,
in Debian we are currently at ITK 4.6 and VTK 6.1 and AFAICS this is
what will go into Jessie. Hence, if you could get a version released
that can be compiled with these two libraries, we could update it,
Note however, that the freeze for Jessie is only a few weeks away.
> Here is
Hi Michael
Sorry that this is causing so much frustration. Unfortunately, ITK and VTK
keep changing fairly rapidly, so code that compiles versus a certain
version no longer compiles against older or later versions.
Here is a table of version compatibility between versions of ITK-SNAP, ITK,
VTK an
Hi,
I am reviving this old thread in order to bring it to an end. Everyone
who has expressed interest and/or frustration in the past is in CC
(incl. the relevant bug).
Over the past month (or rather year) I have repeatedly tried to update
the itksnap package, and today I am giving up. ITK-SNAP ha
29 matches
Mail list logo
