View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013800 | Scribus | Build System | public | 2016-03-08 10:03 | 2016-03-17 08:06 |
| Reporter | Fahad | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | new | Resolution | open | ||
| OS | windows | OS Version | 7,8,10 | ||
| Product Version | 1.5.2.svn | ||||
| Summary | 0013800: enhance windows build instructions | ||||
| Description | There are many missing information about building scribus on windows. Most confusing are bat files which are: 1- copy-dlls-to-15x-build-dir.bat in scribus-common-libs dir. 2- BUILDING_win32_msvc.txt in Scribus src folder. I attached my working files. Also, you have to copy AppIcon.png from 1_5_0 folder to 1_5_1 folder since it is missing. | ||||
| Tags | No tags attached. | ||||
| Patch | No | ||||
|
|
|
|
|
|
|
|
>> There are many missing information about building scribus on windows. Most confusing are bat files which are: 1- copy-dlls-to-15x-build-dir.bat in scribus-common-libs dir. 2- BUILDING_win32_msvc.txt in Scribus src folder. The role of those batch files is already explained in the BUILDING_win32_msvc.txt file in the "INSTALLING RESOURCES AND DEPENDENCIES" section. The section itself already explain their role, so I don't see what should be added. >> Also, you have to copy AppIcon.png from 1_5_0 folder to 1_5_1 folder since it is missing. No, there is already a fallback from 1_5_1 to 1_5_0 folder. The message in command shell is just a warning, not an error. |
|
|
jlpoole is also working on this issue. A recent upstream bug he reported 0013788 |
|
|
@jghali yes the role is explained so that I & khaled could fix the missing files. You can notice that sample script provided in BUILDING_WIN32_MSVC.txt doesn't create 1_5_1 icons folder. Please diff my bat files to see the differences. |
|
|
I had to tinker a lot with the batch files and kept thinking how easy this would be were the build controlled by a Perl script. Do know that one can build Scribus successfully once you have gotten all the batch files to stage the appropriate 32/64 debug & release files. In my opinion the only hurdle here were a few minor changes to bring the code compliant to the compiler shipped with MS Visual Studio 2013 and then sorting out all the staging of the supporting lib and dlls. It's really just a matter of housekeeping - a task Perl is well suited for. |
|
|
I'll attach the DOS batch files which are what I ended up using to stage my files |
|
|
|
|
|
|
|
|
>> You can notice that sample script provided in BUILDING_WIN32_MSVC.txt doesn't create 1_5_1 icons folder. This is false, following line does a recursive copy of the iconsets folder to target directory: xcopy %SCRIBUS_SRC_PATH%\resources\iconsets %SCRIBUS_INSTALL_PATH%\share\icons /s /y /i /D |
|
|
jlpoole, your remarks about manual directory creation in your scripts are wrong. Visual Studio creates build directories and al. automatically. The install steps can be performed with my scripts as is. Perl is not needed at all. |
|
|
Also comment such as "SCRIBUS_LIB_TOOLSET is the version of Microsoft Visual Studio" is not correct. One can perfectly use Visual Studio 2013 and build using Visual Studio 2010 compiler *inside* msvc 2013. The toolset refer to the compiler/linker used, not to the visual studio version. In Visual Studio 2015, one can for example use clang. |
|
|
@Fahad feel free to contact me directly if you encounter further problems. I think my email is publicly exposed from within this bug system -- it's hard to tell if one's email is shown to others here. |
|
|
@jlpoole Thanks. I got scribus built on windows successfully just I opened this bug to share my experience and hoping someone will benift from it. |
|
|
>> I got scribus built on windows successfully just I opened this bug to share my experience and hoping someone will benift from it. The wiki is a better place for that. When a bug is closed, users won't have access to this data anymore unless they search in closed bugs. So really... the wiki is a better place. |
|
|
@Fahad I tested using a clean browser (Chrome instead of Firefox) whether my email is exposed by Mantis and learned it it is not. I'm unable to find a setting that exposes it. So, I'd be interested in having a dialog with you about your experience in building Scribus for Windows and hope you might email me privately at: jlpoole56@gmail.com. I log bugs when I try following instructions and they do not work -- this helps clarify what may seem obvious to the author of the instructions and what could be more helpful to others in the future. My professional experience has been that bugs are an excellent way to communicate and improve a product. Thank you for filing what you did -- it flushed out something I could share and I learned from the experience. |
|
|
a suggestion/question: can we have a github repository with the files and instructions needed for compiling scribus? |
|
|
The instructions are already provided in svn and the files are on sourceforge. There is no need of a github repository. |
|
|
@ale give me another week or two, I'm working on my fork of Scribus at https://github.com/jlpoolen/scribus which will have a Perl-based manager with a text file format that may prove helpful and convenient. |
|
|
jpoole, regarding https://github.com/jlpoolen/scribus/tree/master/win32/vc13, you still confuse Visual Studio marketing name (Visual Studio 2013) with visual studio version (Visual Studio 12.0). There is no such thing called Visual Studio 13.0, so this folder should be called vc12. Also Visual Studio 2015 major version went directly to 14.0. |
|
|
@jghali: Yes, Microsoft marketing can be confusing which probably cost me a lot of time. Your clarification in remark no. https://bugs.scribus.net/view.php?id=13800#c39074 ought to be something that anyone who embarks on compiling Scribus for Windows is made aware of at the very outset, I'll duly make this point featured in the instructions. Thank you for bringing this to my attention and please do not hesitate to call out problems you spot. |
|
|
bump |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-03-08 10:03 | Fahad | New Issue | |
| 2016-03-08 10:03 | Fahad | File Added: copy-dlls-to-15x-build-dir.bat | |
| 2016-03-08 10:04 | Fahad | File Added: resourse.bat | |
| 2016-03-08 11:02 | jghali | Note Added: 0039047 | |
| 2016-03-08 13:42 | Kunda | Note Added: 0039049 | |
| 2016-03-08 13:42 | Kunda | Relationship added | related to 0013788 |
| 2016-03-08 14:01 | Fahad | Note Added: 0039050 | |
| 2016-03-08 14:07 | jlpoole | Note Added: 0039051 | |
| 2016-03-08 14:09 | jlpoole | Note Added: 0039052 | |
| 2016-03-08 14:10 | jlpoole | File Added: copy-dlls-to-15x-build-dir_jlpoole.bat | |
| 2016-03-08 14:14 | jlpoole | File Added: copy-platform-dlls-to-build-dir_jlpoole.bat | |
| 2016-03-08 14:14 | jlpoole | Note Edited: 0039052 | |
| 2016-03-08 14:19 | jghali | Note Added: 0039053 | |
| 2016-03-08 14:27 | jghali | Note Added: 0039054 | |
| 2016-03-08 14:30 | jghali | Note Edited: 0039054 | |
| 2016-03-08 14:58 | jghali | Note Added: 0039055 | |
| 2016-03-08 15:03 | jlpoole | Note Added: 0039056 | |
| 2016-03-08 15:10 | Fahad | Note Added: 0039057 | |
| 2016-03-08 15:11 | jghali | Note Added: 0039058 | |
| 2016-03-08 15:31 | jlpoole | Note Added: 0039059 | |
| 2016-03-08 15:55 | jghali | Note Edited: 0039058 | |
| 2016-03-09 08:36 | ale | Note Added: 0039071 | |
| 2016-03-09 08:52 | jghali | Note Added: 0039072 | |
| 2016-03-09 12:10 | jlpoole | Note Added: 0039073 | |
| 2016-03-09 12:34 | jghali | Note Added: 0039074 | |
| 2016-03-09 12:39 | jlpoole | Note Added: 0039075 | |
| 2016-03-09 12:43 | jlpoole | Note Edited: 0039075 | |
| 2016-03-15 03:17 | Kunda | Note Added: 0039168 | |
| 2016-03-17 08:01 | JLuc | Note Edited: 0039075 | |
| 2016-03-17 08:06 | JLuc | Note Edited: 0039075 |
