View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002149 | Double Commander | Default | public | 2018-10-15 20:15 | 2021-09-05 15:10 |
Reporter | luqman | Assigned To | Alexx2000 | ||
Priority | normal | Severity | minor | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Projection | none | ETA | none | ||
Product Version | 1.0.0 (trunk) | Product Build | 8355 | ||
Target Version | 0.9.0 | Fixed in Version | 0.9.0 | ||
Summary | 0002149: doc/INSTALL.txt: mistake in instructions and small fixes | ||||
Description | Under section 3) Building DC from the command line, there is a typo for the Linux instructions. It says “Use build.sh script to build DC on Windows.” when it should say “Linux.” In addition to this fix I sorted the package files under components/ in alphabetical order. I also added ‘synuni.lpk.’ Last but not least I wrapped lines longer than 80 characters :-) | ||||
Tags | No tags attached. | ||||
Attached Files | INSTALL.txt.diff (3,522 bytes)
Index: doc/INSTALL.txt =================================================================== --- doc/INSTALL.txt (revision 8355) +++ doc/INSTALL.txt (working copy) @@ -7,23 +7,24 @@ 2) Using the IDE to develop and build DC. -If you want to use Lazarus IDE to develop Double Commander, first you have to install -a few additional components all of which reside in components directory of DC sources. -You must open each .lpk package file: +If you want to use Lazarus IDE to develop Double Commander, first you have to +install a few additional components all of which reside in components +directory of DC sources. You must open each .lpk package file: - chsdet/chsdet.lpk - CmdLine/cmdbox.lpk -- multithreadprocs/multithreadprocslaz.lpk - dcpcrypt/dcpcrypt.lpk - doublecmd/doublecmd_common.lpk +- gifanim/pkg_gifanim.lpk - KASToolBar/kascomp.lpk -- gifanim/pkg_gifanim.lpk +- multithreadprocs/multithreadprocslaz.lpk +- synunihighlighter/synuni.lpk - viewer/viewerpackage.lpk -and install it into Lazarus (menu: Package -> Open package file (.lpk) -> Browse to -needed .lpk file -> Press "Install", if "Install" disabled then press "Compile" instead). -Choose "No" when asked for rebuilding Lazarus after each package then rebuild Lazarus -when you have installed all of them. +and install it into Lazarus (menu: Package -> Open package file (.lpk) -> Browse +to needed .lpk file -> Press "Install", if "Install" disabled then press +"Compile" instead). Choose "No" when asked for rebuilding Lazarus after each +package then rebuild Lazarus when you have installed all of them. After rebuilding Lazarus open the project file src/doublecmd.lpi. @@ -36,10 +37,12 @@ Use build.bat script to build DC on Windows. First you need the lazbuild utility of Lazarus to be somewhere in your PATH or -you need to edit the build script and change the lazpath variable to point to it. +you need to edit the build script and change the lazpath variable to point to +it. Execute the script to start the build process. Make sure you use all parameter -if you're building for the first time, so that also components and plugins are built: +if you're building for the first time, so that also components and plugins are +built: > build.bat all @@ -50,19 +53,21 @@ From command line (Linux) -Use build.sh script to build DC on Windows. +Use build.sh script to build DC on Linux. First you need the lazbuild utility of Lazarus to be somewhere in your PATH and -if you installed a Lazarus package it should already be there. Otherwise you need -to edit the build script and change the lazbuild variable to point to it. +if you installed a Lazarus package it should already be there. Otherwise you +need to edit the build script and change the lazbuild variable to point to it. -On Linux two widgetsets are supported: GTK2 or QT4. You can choose one by setting -lcl environment variable before executing the script to either gtk2 or qt, for example: +On Linux two widgetsets are supported: GTK2 or QT4. You can choose one by +setting lcl environment variable before executing the script to either gtk2 or +qt, for example: $ lcl=qt ./build.sh -Execute the script to start the build process. Make sure you use all parameter if -you're building for the first time, so that also components and plugins are built: +Execute the script to start the build process. Make sure you use all parameter +if you're building for the first time, so that also components and plugins are +built: $ ./build.sh all | ||||
Fixed in Revision | 8382 | ||||
Operating system | |||||
Widgetset | |||||
Architecture | |||||
Date Modified | Username | Field | Change |
---|---|---|---|
2018-10-15 20:15 | luqman | New Issue | |
2018-10-15 20:15 | luqman | File Added: INSTALL.txt.diff | |
2018-10-27 12:23 | Alexx2000 | Note Added: 0002840 | |
2018-10-27 12:23 | Alexx2000 | Status | new => acknowledged |
2018-10-27 12:23 | Alexx2000 | Target Version | => 0.9.0 |
2018-10-27 12:54 | Alexx2000 | Fixed in Revision | => 8382 |
2018-10-27 12:54 | Alexx2000 | Status | acknowledged => resolved |
2018-10-27 12:54 | Alexx2000 | Fixed in Version | => 0.9.0 |
2018-10-27 12:54 | Alexx2000 | Resolution | open => fixed |
2018-10-27 12:54 | Alexx2000 | Assigned To | => Alexx2000 |
2021-09-05 15:10 | Alexx2000 | Status | resolved => closed |