Hi All,

Waf is a possible future step... Not a definite move yet. However, at least one of the Inkscape developers has been very impressed by it. Advantages include the fact that it's a python-based tool, so potentially a gentler learning curve than the slightly arcane CMake syntax. Also, it properly supports wildcards, so may be easier to set up and maintain the build. In the meantime, we first need to choose between autotools and CMake so that we can avoid having three build systems in place at once!

In terms of "wasted effort", we already have a mostly ready CMake build, so fixing it shouldn't be too painful, I hope. I haven't done a thorough check yet for missing CMake switches/checks, but this will need to be done as part of any transition, along with documentation.

If there are any patches still outstanding, I'll happily sponsor them.

AV

On 2 Sep 2015 2:04 pm, "Olof Bjarnason" <olof.bjarnason@...400...> wrote:




Mvh


/Olof
-----------------
Trött på virus, seg dator och allmänt Windowsstrul?
Pröva något nytt istället - Ubuntu!

On 2 September 2015 at 14:55, Tobias Ellinghaus <houz@...173...> wrote:
Am Mittwoch, 2. September 2015, 13:15:50 schrieb Alex Valavanis:
> Hi Olof, Shlomi,
>
> autotools builds are the official recommendation for 0.91. CMake still
> needs some work, and doesn't fully support all options.
>
> I think the consensus at present is that supporting two build systems is
> unsustainable and we intend to do the following:
>
> 1. Fix CMake builds for the next release, make this the official build
> system and deprecate the autotools builds.
> 2. Remove the autotools builds in the following release
> 3. Potentially move to the Waf build system in the following release

So all the effort put into CMake are wasted time since you will replace it
with Waf? Why the intermediate step of CMake then?

> Any feedback on your experience with CMake would be greatly appreciated!

For me CMake works nicely, at least for a general build. I didn't add inkview
(i never used that myself) nor did i try to add switches for GTK3 and all the
other options, but plain standard install just works. I build it like this:

mkdir build
cd build
CFLAGS="-O3 -g" CXXFLAGS=${CFLAGS} cmake -DCMAKE_INSTALL_PREFIX=/opt/inkscape/
..
make -j install

Thank you Tobias - but you missed the "../inscape" argument at the end of the cmake command line, right?

Even after fixing that typo, I get the same error as when I got help from Shumis' build script:

CMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:
108 (message):
  Could NOT find JPEG (missing: JPEG_LIBRARY JPEG_INCLUDE_DIR)
Call Stack (most recent call first):
  /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:315 (_FPHSA_F
AILURE_MESSAGE)
  /usr/share/cmake-2.8/Modules/FindJPEG.cmake:31 (FIND_PACKAGE_HANDLE_STANDARD_A
RGS)
  CMakeScripts/DefineDependsandFlags.cmake:184 (FIND_PACKAGE)
  CMakeLists.txt:95 (include) 
 

> AV

Tobias

[...]
------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel



------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...1794...s.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel