Daniel Reetz, the founder of the DIY Book Scanner community, has recently started making videos of prototyping and shop tips. If you are tinkering with a book scanner (or any other project) in your home shop, these tips will come in handy. https://www.youtube.com/channel/UCn0gq8 ... g_8K1nfInQ

Building ST windows executable

Scan Tailor specific announcements, releases, workflows, tips, etc. NO FEATURE REQUESTS IN THIS FORUM, please.
ibr4him
Posts: 102
Joined: 18 Oct 2010, 10:36

Building ST windows executable

Post by ibr4him » 29 Jan 2011, 14:28

Hi,

Although windows binary is available, but i'd like to know how can I build a windows executable from source, has anyone done it yet, any guide available?

Thanks

Tulon
Posts: 687
Joined: 03 Oct 2009, 06:13
Number of books owned: 0
Location: London, UK
Contact:

Re: Building ST windows executable

Post by Tulon » 30 Jan 2011, 09:25

There is a step by step guide in the source archive, in packaging/windows/readme.en.txt

To ensure smooth experience:
1. Use Visual Studio 2008 (express edition will do).
2. Don't use CMake 2.8.3 - use 2.8.2 instead.
3. Don't use Qt 4.6.3 - use 4.6.2 (preferable) or 4.7.x (should work, but less tested).
Scan Tailor experimental doesn't output 96 DPI images. It's just what your software shows when DPI information is missing. Usually what you get is input DPI times the resolution enhancement factor.

ibr4him
Posts: 102
Joined: 18 Oct 2010, 10:36

Re: Building ST windows executable

Post by ibr4him » 30 Jan 2011, 10:37

Awesome! Thanks.

Anonymous1

Re: Building ST windows executable

Post by Anonymous1 » 30 Jan 2011, 10:37

I'm not sure if the stability between versions changes in Linux, but I've been using 4.7.0 with no problems. Maybe it's different for Windows, but at least it works in Linux...

Tulon
Posts: 687
Joined: 03 Oct 2009, 06:13
Number of books owned: 0
Location: London, UK
Contact:

Re: Building ST windows executable

Post by Tulon » 30 Jan 2011, 13:06

It's not about stability. It's about build issues. On Linux, building any kind of program is much easier than on Windows. What's hard on Linux is avoiding building stuff :)
Scan Tailor experimental doesn't output 96 DPI images. It's just what your software shows when DPI information is missing. Usually what you get is input DPI times the resolution enhancement factor.

Anonymous1

Re: Building ST windows executable

Post by Anonymous1 » 30 Jan 2011, 13:13

Heh, it took me a while to figure out all this C++ building stuff. I'm hacking together the bounding box picture zone thing (it's almost done. Just have to get it to work :P ), and those compile errors are just driving me nuts!

This is why I like Python. If Python was as fast as C++, I would have no reason to even use C++. :D

ibr4him
Posts: 102
Joined: 18 Oct 2010, 10:36

Re: Building ST windows executable

Post by ibr4him » 31 Jan 2011, 13:05

Stuck on this:

Code: Select all

Error 13 error LNK1104: cannone open file '..\..\..\bin\moc.exe'
c:\build\scntailor-deps-build\LINK Qt

Tulon
Posts: 687
Joined: 03 Oct 2009, 06:13
Number of books owned: 0
Location: London, UK
Contact:

Re: Building ST windows executable

Post by Tulon » 31 Jan 2011, 13:21

Which version of Qt are you using?
Try with a source-only rather than source+binaries distribution of Qt.
Scan Tailor experimental doesn't output 96 DPI images. It's just what your software shows when DPI information is missing. Usually what you get is input DPI times the resolution enhancement factor.

spamsickle
Posts: 596
Joined: 06 Jun 2009, 23:57

Re: Building ST windows executable

Post by spamsickle » 31 Jan 2011, 15:09

I built from source several times last year on Windows, but then upgraded something and started running into problems. For the past couple of months, I haven't had time to try to track down what I broke. If you're doing this for the first time, I'd recommend trying to get the versions Tulon recommends in his readme file, even though most of them are a couple of years old at this point.

ibr4him
Posts: 102
Joined: 18 Oct 2010, 10:36

Re: Building ST windows executable

Post by ibr4him » 01 Feb 2011, 03:01

Used the version mentioned in the readme except jpeg (it couldn't find jaricom.c in the old version). Still some error, please see the attached log.

Many thanks for your help!
Attachments
log.txt
(1.69 KiB) Downloaded 307 times

Post Reply