The files of a component are spread over all these directories. Both approaches to structure the files in a file system have its assets and drawbacks. To build the SDK some tools are required that are listed in the table below.
Download the tools and install them. The destination directory of each tool is arbitrary. If you are uncertain, choose the default given in the setup dialog of each tool. The contents of the Hugin SDK is shown in the following table. Download the packages, except the packages fetched from Subversion repository. In the following subsections each component is discussed in detail. The order of the subsections seems random, but I applied the approach to describe the precompiled packages first, followed by the big packages, where some of the small packages depend on.
The decompress step of each component contains seemingly inconsistent namings of destination directories, because in some components a subdirectory is specified as destination directory and in some steps only the base directory. This is due to the fact that some package archives contain a base directory and some not. To check the right locations each result section of every component's description contains a summary of the expected files.
In order to make compilation simple, a series of patch files are included below that contain all the necessary changes, not only to compile the SDK, but to optionally compile an x64 version of the SDK. When directed, you will need to apply the patch file specified.
Posted: Sun May 08, am Post subject:. I'm so happy someone created ebuilds for this! I tried to install hugin before and it was really difficult. So, I followed the instructions, and tried Code:. Posted: Sun May 08, pm Post subject:. Okay, I got everything working, but the info and files on this thread is old! Posted: Mon May 09, am Post subject:. You must've missed my updated guide BTW, enblend is in portage now. Posted: Tue May 17, am Post subject:.
I tried Iroko's success story and it worked great for me as well. I got one strange thing with Hugin though. If I try to save as multiple tiffs, hugin saves the individual files but deletes them all when it's finished, strange.
Thanks for the info in this thread, -Jimmy. Posted: Tue May 17, pm Post subject:. This is a known bug in hugin It is fixed as of beta7 which was released yesterday morning. I am trying to get an ebuild for rc1 tested right now but I have not been able to get it to build the digest. My initial testing indicates that beta7 is much more stable than beta4 and also has fixed many, mostly little but anoying, problems.
I have not yet tested rc1 but I suspect that it is mostly beta7 with a few additional fixes. Posted: Wed May 18, pm Post subject:. The idea isn't that you copy the launcher directory to start a new project - it's for the launcher development really. Just copy ChrisPortableApps. Some of the lines in your HuginPortable. If it's not, it's better not to have it as it makes relative files passed in in the command line work. I did already catch some of these, but I appreciate you taking a close look.
The base Hugin app leaves a fairly light touch anyway, so I figured that some of my settings were overkill. I haven't gotten a whole lot of feedback on the function of the app, so I'm going to do all the cleanup you suggested, and post a new beta. I'm hoping to submit it for release sometime in the next month or so, once the format is tighter.
Hi Solanus, Out of interest, now that Hugin 4. I'll have to release another beta, but my biggest issue so far is a lack of feedback on the beta. If you've tried my 2. No problems with your second release here I've updated AND upgraded this test release, since Hugin has started to have a fairly fast release schedule, and I want to have my release as up-to-date as possible when it happens.
Also Chris did a major change to his Launcher, and I wanted to incorporate that. There are too many bugs with the last version of Hugin, I stop testing. However, I haven't found any bug in the portable stuff. Also all the hugin bugs are the same in the portable version of the properly installed version. Even if there are too many bugs, I'd like to know what the biggest ones you've seen are. It IS a complex piece of software, so maybe I haven't found every little niche of it.
Just went to the hugin bug reports on sourceforge and it just happens that I stumbled onto 3 known bugs in about 2 hours If they are known, they will be fixed so I am going to continue to use it. Finally got back to the Hugin project. Unfortunately, one of the tools autopano, for automatically finding control points is no longer included due to patent issues.
You can still download the source, but you have to build it! Are there any plans to have another look at it? I've got a bunch of other irons in the fire right now, but I'll get on it as soon as I can. I notice that they have both bit and bit; I don't know if I should offer both I would assume tht if someone is doing a large project that requires the 64 bit version they would have hugin installed locally.
I would think that the 32 bit version is enough, but that is just my opinion. Posted: Sun Dec 12, pm Post subject: autopano-sift Hi, Modification of hotheads autopano-sift Also, not clear on the guidelines on where to place.
Seems wrong somehow. Copyright Gentoo Technologies, Inc. Posted: Sun Dec 12, pm Post subject:. Posted: Thu Dec 23, am Post subject:. Updated on Jan 18, All ebuilds were updated. The following steps should work, assuming you've done a recent sync Please note: fftw moved from from dev-libs to sci-libs, and this ebuild supports this.
GreenyGianty n00b Joined: 06 Jan Posts: 6. Posted: Sun Jan 09, am Post subject:. Having problems emerging hugin In file included from PointMatching. Posted: Thu Jan 13, pm Post subject:. Me too: Code:. Posted: Sat Jan 15, pm Post subject:. Posted: Sun Jan 16, am Post subject:.
DaMutz wrote:. Posted: Wed Jan 19, am Post subject:. Hi, Above steps were updated using new ebuilds, which includes great contribs by David Grant.
0コメント