March 2015 - macports-tickets - lists.macosforge.org

Re: [MacPorts] #33259: cmake portgroup: out of source build option, possibly by default
by MacPorts 10 Mar '15

10 Mar '15

#33259: cmake portgroup: out of source build option, possibly by default ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by rjvbertin@…): OK... This should do the trick, I think? {{{ diff --git a/trunk/dports/_resources/port1.0/group/cmake-1.0.tcl b/trunk/dports/_resources/port1.0/group/cmake-1.0.tcl --- a/trunk/dports/_resources/port1.0/group/cmake-1.0.tcl (revision 133751) +++ b/trunk/dports/_resources/port1.0/group/cmake-1.0.tcl (working copy) @@ -134,3 +134,17 @@ if {[string first "--enable-debug" ${configure.args}] > -1} { configure.args-delete --enable-debug } + +options cmake.build_out_of_source +default cmake.build_out_of_source false + +if {cmake.build_out_of_source} { + # setup all ports using cmake to build in a separate directory from the source; + # this setting must be the full directory path + post-extract { file mkdir ${workpath}/build } + + # standard post-arg, where to find the primary CMakeLists.txt file. + default configure.post_args {../${worksrcdir}} + default configure.dir {${workpath}/build} + default build.dir {${workpath}/build} +} }}} -- Ticket URL: <https://trac.macports.org/ticket/33259#comment:14> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #33259: cmake portgroup: out of source build option, possibly by default
by MacPorts 10 Mar '15

10 Mar '15

#33259: cmake portgroup: out of source build option, possibly by default ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by michaelld@…): My US$0.02 here: Let's do the global variable boolean optionsas suggested by Mojca that are off by default (for now). When a Portfile sets the value to on/true, we use the VPATH build. In this way, all current ports will still work and we can transition to using the new way as needed and time allows. At some time down the road, we can swap the default value to on/true, and update all of the ports using the CMake portgroup accordingly. -- Ticket URL: <https://trac.macports.org/ticket/33259#comment:13> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #33259: cmake portgroup: out of source build option, possibly by default
by MacPorts 10 Mar '15

10 Mar '15

#33259: cmake portgroup: out of source build option, possibly by default ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by mojca@…): Replying to [comment:11 rjvbertin@…]: > The point with that is: how are you going handle all different build systems? I'm not yet sure about all cases. It's not a big problem for `./configure`. Setting the `configure.dir` and `build.dir` (as well as making one) should be the same. Of course one then needs to call `../<name>/configure` instead of just `./configure`. On the other hand `autotools` would probably have to be run in the same folder as the sources. Of course that wouldn't cover all the cases and even cases with `configure` might fail for many packages simply because they are not properly written and don't support out-of-source builds properly. But leaving maintainers the option to opt in could be useful in some cases. > CMake has a portgroup exactly because it doesn't work the same as the legacy `configure` approach, ditto for qmake and the Python group. So even if base could support OOT builds for the systems it supports, the cmake (etc) portgroup files will still need to redefine the appropriate values. Yes, sure. But we could have a conditional setting. If `Portfile` opts out of default behaviour, the PortGroup should not redefine the values for an out-of-source build. > You wanted a patch? Copying one inline: > > {{{ > diff --git a/trunk/dports/_resources/port1.0/group/cmake-1.0.tcl b/trunk/dports/_resources/port1.0/group/cmake-1.0.tcl > --- a/trunk/dports/_resources/port1.0/group/cmake-1.0.tcl (revision 133751) > +++ b/trunk/dports/_resources/port1.0/group/cmake-1.0.tcl (working copy) > @@ -134,3 +134,13 @@ > if {[string first "--enable-debug" ${configure.args}] > -1} { > configure.args-delete --enable-debug > } > + > +# setup all ports using cmake to build in a separate directory from the source; > +# this setting must be the full directory path > +post-extract { file mkdir ${workpath}/build } > + > +# standard post-arg, where to find the primary CMakeLists.txt file. > +default configure.post_args {../${worksrcdir}} > +default configure.dir {${workpath}/build} > +default build.dir {${workpath}/build} > + > }}} It would probably help if we had some (very) basic configurability to opt out. -- Ticket URL: <https://trac.macports.org/ticket/33259#comment:12> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #33259: cmake portgroup: out of source build option, possibly by default
by MacPorts 10 Mar '15

10 Mar '15

#33259: cmake portgroup: out of source build option, possibly by default ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by rjvbertin@…): The point with that is: how are you going handle all different build systems? CMake has a portgroup exactly because it doesn't work the same as the legacy `configure` approach, ditto for qmake and the Python group. So even if base could support OOT builds for the systems it supports, the cmake (etc) portgroup files will still need to redefine the appropriate values. You wanted a patch? Copying one inline: {{{ diff --git a/trunk/dports/_resources/port1.0/group/cmake-1.0.tcl b/trunk/dports/_resources/port1.0/group/cmake-1.0.tcl --- a/trunk/dports/_resources/port1.0/group/cmake-1.0.tcl (revision 133751) +++ b/trunk/dports/_resources/port1.0/group/cmake-1.0.tcl (working copy) @@ -134,3 +134,13 @@ if {[string first "--enable-debug" ${configure.args}] > -1} { configure.args-delete --enable-debug } + +# setup all ports using cmake to build in a separate directory from the source; +# this setting must be the full directory path +post-extract { file mkdir ${workpath}/build } + +# standard post-arg, where to find the primary CMakeLists.txt file. +default configure.post_args {../${worksrcdir}} +default configure.dir {${workpath}/build} +default build.dir {${workpath}/build} + }}} That's copied over directly from the KDE4 1.1 portgroup, with just a slight change in the comment. -- Ticket URL: <https://trac.macports.org/ticket/33259#comment:11> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #33259: cmake portgroup: out of source build option, possibly by default
by MacPorts 10 Mar '15

10 Mar '15

#33259: cmake portgroup: out of source build option, possibly by default ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by mojca@…): We could introduce a global variable like `build_in_source yes/no` or `build_out_of_source yes/no` that would default to in-source while the CMake PortGroup could set it to out-of-source by default. Individual ports could then opt in or out and the functionality wouldn't be limited to the CMake PortGroup alone. -- Ticket URL: <https://trac.macports.org/ticket/33259#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #33259: cmake portgroup: out of source build option, possibly by default
by MacPorts 10 Mar '15

10 Mar '15

#33259: cmake portgroup: out of source build option, possibly by default ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by mojca@…): Before dreaming about setting up new buildslaves, it would help to actually come up with a patch ;) -- Ticket URL: <https://trac.macports.org/ticket/33259#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #46690: gdal ogr not supported
by MacPorts 10 Mar '15

10 Mar '15

#46690: gdal ogr not supported -------------------------------+-------------------------------- Reporter: barry.j.mcinnes@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: gdal ogr | Port: gdal -------------------------------+-------------------------------- We get this error on 10.9 and 10.10 Macports updated as of last week. Not sure if its a Macports install or user error, it seems to have been an issue with gdal 1.7 ? [mac27:~] bmcinnes% gdal-config --ogr-enabled yes [mac27:~] bmcinnes% gdalwarp -cutline /Users/blivneh/Research/NLDAS/Shapefiles_MAY2005/Original_Features/Mexican_Cuencas.shp -crop_to_cutline -dstnodata "-9999.0" del.mask.tiff del.mask.clipped.tiff ERROR 1: Request to load a cutline failed, this build does not support OGR features. [mac27:~] bmcinnes% gdal-config --version 1.11.1 [mac27:~] bmcinnes% which gdal-config /opt/local/bin/gdal-config [mac27:~] bmcinnes% port info gdal gdal @1.11.1_3 (gis) Variants: clang30, clang31, clang32, clang33, clang34, clang35, curl, dragonegg30, dragonegg31, dragonegg32, dragonegg33, dragonegg34, ecw, [+]expat, framework, gcc44, gcc45, gcc46, gcc47, gcc48, gcc49, geos, grib, hdf4, hdf5, jasper, llvm, lzma, mpich, mpich_devel, mrsid, mysql5, netcdf, odbc, opencl, openjpeg, openmpi, openmpi_devel, perf, poppler, postgresql81, postgresql82, postgresql83, postgresql84, postgresql90, postgresql91, postgresql92, postgresql93, spatialite, sqlite3, universal, xerces Description: GDAL is a translator library for raster geospatial data formats that is released under an X/MIT style Open Source license. As a library, it presents a single abstract data model to the calling application for all supported formats. The related OGR library (which lives within the GDAL source tree) provides a similar capability for simple features vector data. Homepage: http://www.gdal.org/ Library Dependencies: zlib, libpng, tiff, libgeotiff, jpeg, giflib, proj, expat Platforms: darwin License: MIT BSD Maintainers: vince(a)macports.org, openmaintainer(a)macports.org [mac27:~] bmcinnes% -- Ticket URL: <https://trac.macports.org/ticket/46690> MacPorts <https://www.macports.org/> Ports system for OS X

1 11

[MacPorts] #47041: Update: wireshark 1.12.4
by MacPorts 10 Mar '15

10 Mar '15

#47041: Update: wireshark 1.12.4 ----------------------------+-------------------------------- Reporter: mschamschula@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: h | Port: wireshark ----------------------------+-------------------------------- wireshark has been updated to version 1.12.4. -- Ticket URL: <https://trac.macports.org/ticket/47041> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

Re: [MacPorts] #33259: cmake portgroup: out of source build option, possibly by default
by MacPorts 10 Mar '15

10 Mar '15

#33259: cmake portgroup: out of source build option, possibly by default ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by rjvbertin@…): I agree. The KDE4 PortGroup imposes this, in a way that appears to work just fine with all KDE4 ports. Maybe the only way to advance this (3yo!) ticket is to force the change and see what ports break? (It would be nice if MacPorts had a build slave that could do this testing and then send note to the maintainers of ports that get broken...) -- Ticket URL: <https://trac.macports.org/ticket/33259#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #25259: gimp2 2.6.8 online help does not open
by MacPorts 10 Mar '15

10 Mar '15

#25259: gimp2 2.6.8 online help does not open -------------------------+---------------------- Reporter: swebster@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.0 Resolution: | Keywords: Port: gimp2 | -------------------------+---------------------- Comment (by devans@…): Yes, but the error mode has changed from that described. In GIMP 2.6, this menu selection used gvfs to access the online web site which led to the reported error. The underlying cause is with gvfs (#32652) which still has not been fixed. By default, GIMP 2.8 now uses the built-in, webkit-gtk based, help browser which successfully accesses the online help server but the URL provided is invalid. {{{ Not Found The requested URL /2.8/en_US.UTF-8/index.html was not found on this server. Apache Server at docs.gimp.org Port 80 }}} This is because the online help web site only supports a limited set of locales using the two-letter format only. For example, to get help in English the proper URL is http://docs.gimp.org/2.8/en/index.html. The work around for this is to use the locally installed help (the default help preferences setting, which is now relatively up to date, although this is only available in English. -- Ticket URL: <https://trac.macports.org/ticket/25259#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X

1 0