I'd like to tackle the find-the-font issue. CMake installs the font to a
platform-specific location. The easiest way to deal with that is to
simply hard-code this location in the C++ code and have it differ
between the branches, so in the master branch I've modified the code
pv_no_rendering.cc accordingly. It now does this:
- if the user has passed a font on the CL, that takes preference.
- next, lux will check the pwd. if the font isn't there
- lux will try and access the target-specific location, assuming it has
been installed on the local machine
- if that fails, lux will exit
I've groomed the CMakeLists.txt a bit and also added code to copy the
Font's README to the font path, as required by the font's license.
For now I've only changed the master branch to this behaviour, so you
can try it out. Let me know what you think. If this works satisfactorily
on linux, I'll change the other branches accordingly.
@Harry: can you please tell me what path the font is installed to on the
mac, so I can adapt the mac branch?
I did a trial 'sudo make install' on my machine and it works fine. I
don't like having platform-specific code, but for this single issue I
can just about live with it ;)
The last push to master also should have resolved an issue with
stitching images with alpha channel, so 'manual deghosting' by erasing
unwanted bits from partials where other partials have content to 'fill
the gap' should now work as expected for stitches - exposure fusions and
faux brackets weren't affected.
I'll carry on grooming and refactoring for a while, and I may be able to
save some more memory. With the last commit, I already introduced new
code which only uses single-float masks, where pv had used RGB data for
convenience's sake. This should already have produced the bulk of memory
savings I think possible.
@Harry: please check memory use again, let me know how far I got memory
consumption down, and if the lowering of the number of threads with
--snapshot_threads now works for you.
Kay
--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/c9dea6ca-5672-c902-1be4-2df5ff9385e7%40yahoo.com.
