| Re: Solved
Oct 17 2006 on content Reveal |
Great, modification now in SVN. |
|  | | Re: Error compiling
Oct 17 2006 on content Reveal |
Hrmm, apparently you've gotten almost all the way to getting Reavel compiled but are failing during linking because it cannot find various libtiff symbols. You must have the libtiff includes installed to have gotten this far. Oh jeesh. I bet I know the problem, I hadn't tested compiling Reveal dynamically under Linux.
If you look under projects/libraries.pri under the linux section you'llnotice I didn't add a rule for linking with libtiff . try adding the following to the top of the libraries.pri file:
contains(CONFIG, libtiff) LIBS += -ltiff
Please let me know if that fixes the problem so I can patch the code in SVN |
| | | Re: Re: Re: error :(
May 10 2006 on content Reveal |
Instead of say "Build will require XXX" I really should print out "Build will USE XXXX". Those are not error messages, they're just announcements, letting you know we'll be linking against those libraries. Try running make and make install. Building will probably work just fine.
Another user made the same comment. He was sure somethign was not working properly when everything was fine. I've changed the code in SVN such that future releases will be less confusing. |
| | | Re: error :(
Oct 28 2005 on content Reveal |
You need to download the latest exiv2 sources from Andreas's svn respository, then edit Reveal.pro to point to the correct location to find the includes libraries when linking. In the future building Reveal will bemuch easier when exiv2 includes a tool for determing this information automatically much like the xml2 and xslt libraries do today. Sorry about this.
exiv2 web site:
http://home.arcor.de/ahuggel/exiv2/
svn command to get latest code (0.7 will NOT work)
svn checkout svn://dev.robotbattle.com/exiv2/trunk .
-will |
| | | Re: default album
Apr 12 2005 on content Album Shaper |
I've taken the word processor approach, which I think is best for now since many people create many albums. In the future this may change, and if so you'll be a happy man. Until then, save your wrist some work and just hit Ctrl+1 to load most recent album when you start up. Ctrl+2, 3, and so on should also work. ;-) |
| | | Re: Re: Album Manage
Apr 12 2005 on content Album Shaper |
Several users have asked for this functionality, and I looked into it for 2.1. Unfortunately, supporting importing both files and directories within the same add dialog (which would be optimal IMHO) is hokey using the Qt file dialogs. I'd also prefer to provide native KDE file dialogs (also requested) for KDE'ers, especially since KDE provides nice way to extend such dialogs for adding stuff like improved file previes, etc. I've marked this request as a much have under the future tasks list that all can now follow by visiting:
http://albumshaper.sourceforge.net/futurePlans.shtml
If I've forgotten a feature request anyone has sent me in the past it is not intentional. Send me a message and I'll be sure to update this list. |
| | | Re: Thread safe?
Mar 16 2005 on content Album Shaper |
This problem is now fixed in CVS. Thank you for reporting it. |
| | | Re: Seems great but.
Mar 16 2005 on content Album Shaper |
Just checked the necessary changes into CVS. You can now easily change both where the binary and where the resources are installed, and now the defaults are /usr/bin and /usr/share. Other minor errors like qmake trying to strip the install script are also fixed. |
| | | Re: Re: Re: Seems gr
Mar 15 2005 on content Album Shaper |
I just realized this problem (you have to modify the main.cpp file) myself. Thanks for pointing this out. I'm refactoring the AlbumShaper.pro and main.cpp files a bit right now and will post again here when a fix is in CVS so you can more easily change the install locations. The pro file will be a lot simpler now too. You should not need to update the .xcode files though. If you want to compile Album Shaper using xcode run the "createXCodeProject" script. Somehow I doubt many people will be compiling Album Shaper from source for their OSX systems since I provide a binary for them already... |
| | | Re: Seems great but.
Mar 15 2005 on content Album Shaper |
If you want to install Album Shaper to a location other than /usr/local/[bin:share] then just edit the AlbumShaper.pro file and replace all references to these paths, rerun qmake, then do a Make install. I'll see if I can refactor the .pro file a bit so you can specify this in one place up top. I always found /usr/local/ to be the standard place to put user centric software I'm an old Slackware user. Where do most people install stuff these days? |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
