Am Donnerstag, 27. Januar 2011 schrieb kfj:
> On 27 Jan., 11:04, Kornel Benko wrote:
> > You have always to learn. 'lazy' is valid for simple tasks only.
>
> Kornel, thank you for your help. Now I think I can set it up to my
> satisfaction.
Nice to hear ...
> I hope you don't mind me moaning ab
On 27 Jan., 11:04, Kornel Benko wrote:
> You have always to learn. 'lazy' is valid for simple tasks only.
Kornel, thank you for your help. Now I think I can set it up to my
satisfaction. I hope you don't mind me moaning about cmake, in the end
it can be persuaded to do the right thing and once
Am Donnerstag, 27. Januar 2011 schrieb kfj:
> On 26 Jan., 21:34, Kornel Benko wrote:
> > You have to define a dependency
> >
> > e.g.
> > add_custom_command(
> > ...
> > DEPENDS zz.i
> > )
>
> So I tried this:
>
> IF(MSVC)
> SET(PREPROCESSO
On 26 Jan., 21:34, Kornel Benko wrote:
> You have to define a dependency
>
> e.g.
> add_custom_command(
> ...
> DEPENDS zz.i
> )
So I tried this:
IF(MSVC)
SET(PREPROCESSOR_FLAGS "/EP")
ELSE()
SET(PREPROCESSOR_FLAGS "-E")
ENDIF()
SET(C_PR
Am Mittwoch, 26. Januar 2011 schrieb kfj:
> On 26 Jan., 12:37, Kornel Benko wrote:
> > But, why not rename xx.h into xx.cpp?
>
> Hey, no problem, I can rename it into anything. So let's assume I have
> zz.cpp in my source directory and I want it to be C-preprocessed into
> a file z.i in my binary
On 26 Jan., 12:37, Kornel Benko wrote:
> But, why not rename xx.h into xx.cpp?
Hey, no problem, I can rename it into anything. So let's assume I have
zz.cpp in my source directory and I want it to be C-preprocessed into
a file z.i in my binary directory, from where it's included into
another f
Am Mittwoch, 26. Januar 2011 schrieb kfj:
> Hi all!
>
> I'm still struggling with cmake for hsi/hpi, and I just can't get my
> head round it's strange ways, and what online documentation there is I
> don't find helpful either. So maybe someone can help me with this
> simple problem:
>
> I have a
Hi all!
I'm still struggling with cmake for hsi/hpi, and I just can't get my
head round it's strange ways, and what online documentation there is I
don't find helpful either. So maybe someone can help me with this
simple problem:
I have a C++ header file zz.h in my source directory
I want this
On 20 Jan., 18:41, "T. Modes" wrote:
> Hi Kay,
>
> > > > Help with these problems would be greatly appreciated
>
> > > That was, help with cmake, as stated on the thread headline and
>
> I sent you yesterday a patch with a modified cmake system, which fixes
> most of the problems (I commited it
Hi Kay,
> > > Help with these problems would be greatly appreciated
>
> > That was, help with cmake, as stated on the thread headline and
I sent you yesterday a patch with a modified cmake system, which fixes
most of the problems (I commited it in the meanwhile to the
repository).
Thomas
--
Yo
On 20 Jan., 09:53, kfj <_...@yahoo.com> wrote:
> On 18 Jan., 16:47, kfj <_...@yahoo.com> wrote:
>
> > Help with these problems would be greatly appreciated
>
> That was, help with cmake, as stated on the thread headline and
> ...
oops... I'm sorry, I'll have to swallow my words, since the proble
On 18 Jan., 16:47, kfj <_...@yahoo.com> wrote:
> Help with these problems would be greatly appreciated
That was, help with cmake, as stated on the thread headline and
requested in the initial posting. I would really appreciate if someone
could actually at least touch the issue. I set up a thread
On 19 Jan., 20:49, "T. Modes" wrote:
> Hi Kay,
>
> On 19 Jan., 09:32, kfj <_...@yahoo.com> wrote:
>
> > This may work, but is
> > it necessary? Until then, as posted previously, use the getVar()
> > method as a workaround.
>
> Yes, it is necessary. The workaround works only for some variables
>
Hi Kay,
On 19 Jan., 09:32, kfj <_...@yahoo.com> wrote:
> This may work, but is
> it necessary? Until then, as posted previously, use the getVar()
> method as a workaround.
Yes, it is necessary. The workaround works only for some variables
like yaw, pitch and so on. But with this I don't get e.g.
On 19 Jan., 09:21, kfj <_...@yahoo.com> wrote:
> On 18 Jan., 20:35, "T. Modes" wrote:
>
> > Hi Pablo,
>
> > > > But I found an issue: I can not access the image variables of
> > > > SrcPanoImage like getImage(0).getYaw() and so on
> I'll have a lok and see if I can figure out what's amiss.
In
On 18 Jan., 20:35, "T. Modes" wrote:
> Hi Pablo,
>
> > > But I found an issue: I can not access the image variables of
> > > SrcPanoImage like getImage(0).getYaw() and so on
you're right, they're not inside. For now you'll have to use
img.getVar('y')
I'll have a lok and see if I can figure ou
On 18 Jan., 20:35, "T. Modes" wrote:
Hi guys!
I've just uploaded a recent tar file with all the code needed to run
Python plugins from hugin. You may want this - the hsi part is pretty
unchanged, but the plugin interface for hugin is new. You may want to
wait until I have a modified hugin repo
Hi Pablo,
> > But I found an issue: I can not access the image variables of
> > SrcPanoImage like getImage(0).getYaw() and so on
>
> Thats probably because these functions are defined using some macros
> inside Panorama.h.
I assumed the same. But they are defined in SrcPanoImage.h/.cpp and
not in
Hi Thomas,
Am 18.01.2011 19:24, schrieb T. Modes:
But I found an issue: I can not access the image variables of
SrcPanoImage like getImage(0).getYaw() and so on
Thats probably because these functions are defined using some macros
inside Panorama.h. Maybe swig needs to call the C preprocessor
> PS: I tried hsi on windows. It compiles. But the generated lib is
> called _hsi.pyd (not hsi.pyd).
> And when I try to run in python your example, I'm getting errors. I
> can run the procedure, but I'm can access the object:
>
Update. Accessing the pano object works now (needed to copy a file).
On 18 Jan., 16:47, kfj <_...@yahoo.com> wrote:
> That works well and automatically generates the relevant wrapper files
> hsi.py and _hsi.so, but so far I haven't found a way of telling Cmake
> to also generate above-mentioned header file swigpyrun.h. It's not
> totally crucial to generate it fr
21 matches
Mail list logo
