Hi, thanks for the feedback. I thought there might be some conflict between btool and cmake, so I did another trial. I did a lightweight checkout of 0.92.x branch rev 15275. I put this into a new directory, never used before, and ran the test again. The results are the same as before, as below: I am attaching the CMakeOutput.log file. The machine that I do the build on is not connected to the internet so I am not able to run the 'bzr status' command. CMakeOutput.log http://inkscape.13.x6.nabble.com/file/n4978233/CMakeOutput.log Cheers, Alvin

................................................................ C:\InkscapeBZR92x\src>md build

C:\InkscapeBZR92x\src>cd build

C:\InkscapeBZR92x\src\build>cmake -G "MinGW Makefiles" .. -- The C compiler identification is GNU 4.6.1 -- The CXX compiler identification is GNU 4.6.1 -- Check for working C compiler: c:/mingw/bin/gcc.exe -- Check for working C compiler: c:/mingw/bin/gcc.exe -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: c:/mingw/bin/g++.exe -- Check for working CXX compiler: c:/mingw/bin/g++.exe -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Error at debug/CMakeLists.txt:28 (add_inkscape_source): Unknown CMake command "add_inkscape_source".

CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required command is present. A line of code such as

cmake_minimum_required(VERSION 3.2)

should be added at the top of the file. The version specified may be lower if you wish to support older CMake versions for this project. For more information run "cmake --help-policy CMP0000". This warning is for project developers. Use -Wno-dev to suppress it.

-- Configuring incomplete, errors occurred! See also "C:/InkscapeBZR92x/src/build/CMakeFiles/CMakeOutput.log".

-- View this message in context: http://inkscape.13.x6.nabble.com/unable-to-compile-0-92-x-rev-15268-on-Windo... Sent from the Inkscape - Dev mailing list archive at Nabble.com.

Am 22.12.2016 um 01:49 schrieb Sylvain Chiron:

Le 22/12/2016 à 01:44, alvinpenner a écrit :

...

 The machine that I do the build on is not connected to the internet so I

am not able to run the 'bzr status' command.

I don’t think you need an internet connection to run bzr status… Unless you don’t have Bazaar. Did you try to use a more recent version of CMake?

That's what I had in mind and assume to be the prime suspect (maybe I should have been clearer).

...

CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required command is present. A line of code such as cmake_minimum_required(VERSION 3.2) should be added at the top of the file.

Shouldn’t we add this command?

It's there... No idea what CMake is doing (or rather not doing) to produce this message.

-- Sylvain

---

Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Oh, I think there's the issue (it seems it was just too obvious...): You have to create the "build" folder in your root directory, not the "/src" subdirectory!

Am 22.12.2016 um 03:41 schrieb alvinpenner:

Hi, I upgraded from CMake 3.2.1 to 3.7.1 but the result is the same. I am attaching a portion of the directory tree underneath src. To me this looks rather strange. Is it normal to have two different debug directories and two different CMakeFiles directories? I followed the instructions on the website, but the resulting tree looks unusual.

Alvin

C:\InkscapeBZR92x\src>tree Folder PATH listing Volume serial number is 68EA-76E1 C:. ├───2geom │ └───numeric ├───build │ ├───CMakeFiles │ │ ├───3.7.1 │ │ │ ├───CompilerIdC │ │ │ └───CompilerIdCXX │ │ └───CMakeTmp │ └───debug │ └───CMakeFiles ├───debug ├───display ├───extension │ ├───dbus │ │ ├───doc │ │ └───wrapper │ ├───implementation │ ├───internal │ │ ├───bitmap │ │ ├───filter │ │ └───pdfinput │ ├───param │ └───plugins │ └───grid2 ├───filters ├───helper ├───inkgc

-- View this message in context: http://inkscape.13.x6.nabble.com/unable-to-compile-0-92-x-rev-15268-on-Windo... Sent from the Inkscape - Dev mailing list archive at Nabble.com.

---

Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

thanks again, the build was successful. just 2 final questions:

1. I am getting the warnings about hicolor again:

C:\InkscapeBZR92x\build\output\InkscapeBZR92x\build\inkscape>inkscape -V Inkscape 0.92pre4

C:\InkscapeBZR92x\build\output\InkscapeBZR92x\build\inkscape>inkscape

(inkscape.exe:2240): Gtk-WARNING **: Could not find the icon 'object-visible'. The 'hicolor' theme was not found either, perhaps you need to install it. You can get a copy from: http://icon-theme.freedesktop.org/releases

2. I cannot seem to find the gdb.exe file anywhere in the output. Is it intended that it should be included, for debugging purposes? Or, I guess what I mean is, will it be included if you compile trunk using cmake?

Alvin

-- View this message in context: http://inkscape.13.x6.nabble.com/unable-to-compile-0-92-x-rev-15268-on-Windo... Sent from the Inkscape - Dev mailing list archive at Nabble.com.

Hi, thanks for the feedback. I have been able to locate the index.theme file, it is located at:

C:\InkscapeBZR92x\build>dir/s index.theme Volume in drive C has no label. Volume Serial Number is 68EA-76E1

Directory of C:\InkscapeBZR92x\build\inkscape\share\icons\hicolor

12/21/2016 10:11 PM 40 index.theme

unfortunately, that is not where the inkscape executable is located. The executable is at:

Directory of C:\InkscapeBZR92x\build\output\InkscapeBZR92x\build\inkscape

12/21/2016 11:02 PM 1,568,913 inkscape.exe

so it is unlikely that the executable will find the required hicolor directory. Attached is a directory listing of the hicolor directory that inkscape is using

Directory of C:\InkscapeBZR92x\build\output\InkscapeBZR92x\build\inkscape\share\icons\hicolor

12/21/2016 11:17 PM <DIR> . 12/21/2016 11:17 PM <DIR> .. 12/21/2016 11:17 PM <DIR> 16x16 12/21/2016 11:17 PM <DIR> 22x22 12/21/2016 11:17 PM <DIR> 24x24 12/21/2016 11:17 PM <DIR> 256x256 12/21/2016 11:17 PM <DIR> 32x32 12/21/2016 11:17 PM <DIR> 48x48

It does not contain the index.theme file. Obviously I have located the inkscape build output into the wrong directory, but it is not entirely clear what the right location would be.

Would it be possible, on the website http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows to indicate two things: 1. where is the build directory supposed to be relative to the src? 2. where is the output directory supposed to be relative to the src? 3. or perhaps a typical directory tree would be helpful on the website, showing the relative locations of the various directories? 4. or perhaps an explicit example showing the exact format of the mingw32-make command, including the source directory from which it was executed, similar to what the btool documentation shows?

.....................................................

wrt the gdb.exe file, I guess it doesn't matter for the 0.92.x branch, as long as a typical trunk build will include it, as well as the inkscape.dbg file.

thanks for your patience, Alvin

-- View this message in context: http://inkscape.13.x6.nabble.com/unable-to-compile-0-92-x-rev-15268-on-Windo... Sent from the Inkscape - Dev mailing list archive at Nabble.com.

yes, I think that is correct. I believe that I was in the 'build' directory, and I created the 'output' directory, and then I used the command 'mingw32-make DESTDIR=output install'. next time I'll try it without the DESTDIR.

thanks for the advice, Alvin

-- View this message in context: http://inkscape.13.x6.nabble.com/unable-to-compile-0-92-x-rev-15268-on-Windo... Sent from the Inkscape - Dev mailing list archive at Nabble.com.