Re: creating makefile for new pgadmin4 port: qmake error
You have to build outsource so:
USES= pgsql python qmake:outsource qt:5
QMAKE_SOURCE_PATH= ${WRKSRC}/runtime
Good luck for the next steps
Loïc
Le 13/09/2018 à 22:03, Marco Beishuizen a écrit :
Hi,
I'm trying to create a port for pgadmin4. If I follow the instructions
in the readme file for building from source (first a qmake and the a
make), all works fine and the pgAdmin4 binary is build.
Next step is to create the makefile for the port. So far I have:
[...]
PORTNAME= pgadmin4
PORTVERSION= 3.3
CATEGORIES= databases
MASTER_SITES= PGSQL/pgadmin/pgadmin4/v${PORTVERSION}/source/
DISTNAME= pgadmin4-${PORTVERSION}
MAINTAINER= mb...@xs4all.nl
COMMENT= PostgreSQL Administration Tool
LICENSE= PostgreSQL
BUILD_DEPENDS sphinx-build:textproc/py-sphinx
USES= pgsql python qmake qt:5
USE_QT= core gui network widgets
.include
[...]
The error I get at this point is that qmake doesn't seem to work:
[...]
===> License PostgreSQL accepted by the user
===> pgadmin4-3.3 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by pgadmin4-3.3 for building
===> Extracting for pgadmin4-3.3
=> SHA256 Checksum OK for pgadmin4-3.3.tar.gz.
===> Patching for pgadmin4-3.3
===> pgadmin4-3.3 depends on file: /usr/local/bin/python2.7 - found
===> pgadmin4-3.3 depends on file: /usr/local/lib/qt5/bin/qmake - found
===> pgadmin4-3.3 depends on shared library: libpq.so.5 - found
(/usr/local/lib/libpq.so.5)
===> pgadmin4-3.3 depends on shared library: libQt5Core.so - found
(/usr/local/lib/qt5/libQt5Core.so)
===> pgadmin4-3.3 depends on shared library: libQt5Gui.so - found
(/usr/local/lib/qt5/libQt5Gui.so)
===> pgadmin4-3.3 depends on shared library: libQt5Network.so -
found (/usr/local/lib/qt5/libQt5Network.so)
===> pgadmin4-3.3 depends on shared library: libQt5Widgets.so -
found (/usr/local/lib/qt5/libQt5Widgets.so)
===> Configuring for pgadmin4-3.3
Usage: /usr/local/lib/qt5/bin/qmake [mode] [options] [files]
QMake has two modes, one mode for generating project files based on
some heuristics, and the other for generating makefiles. Normally you
shouldn't need to specify a mode, as makefile generation is the default
mode for qmake, but you may use this to test qmake on an existing project
Mode:
-project Put qmake into project file generation mode
In this mode qmake interprets files as files to
be built,
defaults to *; *; *; *.ts; *.xlf; *.qrc
Note: The created .pro file probably will
need to be edited. For example add the QT variable to
specify what modules are required.
-makefile Put qmake into makefile generation mode (default)
In this mode qmake interprets files as project files to
be processed, if skipped qmake will try to find a
project
file in your current working directory
Warnings Options:
-Wnone Turn off all warnings; specific ones may be
re-enabled by
later -W options
-Wall Turn on all warnings
-Wparser Turn on parser warnings
-Wlogic Turn on logic warnings (on by default)
-Wdeprecated Turn on deprecation warnings (on by default)
Options:
* You can place any variable assignment in options and it will be *
* processed as if it was in [files]. These assignments will be *
* processed before [files] by default. *
-o file Write output to file
-d Increase debug level
-t templ Overrides TEMPLATE as templ
-tp prefix Overrides TEMPLATE so that prefix is prefixed into
the value
-help This help
-v Version information
-early All subsequent variable assignments will be
parsed right before default_pre.prf
-before All subsequent variable assignments will be
parsed right before [files] (the default)
-after All subsequent variable assignments will be
-late All subsequent variable assignments will be
parsed right after default_post.prf
-norecursive Don't do a recursive search
-recursive Do a recursive search
-set Set persistent property
-unset Unset persistent property
-query Query persistent property. Show all if is empty.
-qtconf file Use file instead of looking for qt.conf
-cache file Use file as cache [makefile mode only]
-spec spec Use spec as QMAKESPEC [makefile mode only]
-nocache Don't use a cache file [makefile mode only]
-nodepend Don't generate dependencies [makefile mode only]
-nomoc Don't generate moc targets [makefile mode only]
-nopwd Don't look for files in pwd [project mode only]
*** Error code 1
Stop.
make: stopped in /home/marco/devel/_freebsd/ports/databas
creating makefile for new pgadmin4 port: qmake error
Hi,
I'm trying to create a port for pgadmin4. If I follow the instructions in
the readme file for building from source (first a qmake and the a make),
all works fine and the pgAdmin4 binary is build.
Next step is to create the makefile for the port. So far I have:
[...]
PORTNAME= pgadmin4
PORTVERSION=3.3
CATEGORIES= databases
MASTER_SITES= PGSQL/pgadmin/pgadmin4/v${PORTVERSION}/source/
DISTNAME= pgadmin4-${PORTVERSION}
MAINTAINER= mb...@xs4all.nl
COMMENT=PostgreSQL Administration Tool
LICENSE=PostgreSQL
BUILD_DEPENDS sphinx-build:textproc/py-sphinx
USES= pgsql python qmake qt:5
USE_QT= core gui network widgets
.include
[...]
The error I get at this point is that qmake doesn't seem to work:
[...]
===> License PostgreSQL accepted by the user
===> pgadmin4-3.3 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by pgadmin4-3.3 for building
===> Extracting for pgadmin4-3.3
=> SHA256 Checksum OK for pgadmin4-3.3.tar.gz.
===> Patching for pgadmin4-3.3
===> pgadmin4-3.3 depends on file: /usr/local/bin/python2.7 - found
===> pgadmin4-3.3 depends on file: /usr/local/lib/qt5/bin/qmake - found
===> pgadmin4-3.3 depends on shared library: libpq.so.5 - found
(/usr/local/lib/libpq.so.5)
===> pgadmin4-3.3 depends on shared library: libQt5Core.so - found
(/usr/local/lib/qt5/libQt5Core.so)
===> pgadmin4-3.3 depends on shared library: libQt5Gui.so - found
(/usr/local/lib/qt5/libQt5Gui.so)
===> pgadmin4-3.3 depends on shared library: libQt5Network.so - found
(/usr/local/lib/qt5/libQt5Network.so)
===> pgadmin4-3.3 depends on shared library: libQt5Widgets.so - found
(/usr/local/lib/qt5/libQt5Widgets.so)
===> Configuring for pgadmin4-3.3
Usage: /usr/local/lib/qt5/bin/qmake [mode] [options] [files]
QMake has two modes, one mode for generating project files based on
some heuristics, and the other for generating makefiles. Normally you
shouldn't need to specify a mode, as makefile generation is the default
mode for qmake, but you may use this to test qmake on an existing project
Mode:
-project Put qmake into project file generation mode
In this mode qmake interprets files as files to
be built,
defaults to *; *; *; *.ts; *.xlf; *.qrc
Note: The created .pro file probably will
need to be edited. For example add the QT variable to
specify what modules are required.
-makefile Put qmake into makefile generation mode (default)
In this mode qmake interprets files as project files to
be processed, if skipped qmake will try to find a project
file in your current working directory
Warnings Options:
-Wnone Turn off all warnings; specific ones may be re-enabled by
later -W options
-Wall Turn on all warnings
-Wparser Turn on parser warnings
-WlogicTurn on logic warnings (on by default)
-Wdeprecated Turn on deprecation warnings (on by default)
Options:
* You can place any variable assignment in options and it will be *
* processed as if it was in [files]. These assignments will be*
* processed before [files] by default.*
-o fileWrite output to file
-d Increase debug level
-t templ Overrides TEMPLATE as templ
-tp prefix Overrides TEMPLATE so that prefix is prefixed into the
value
-help This help
-v Version information
-early All subsequent variable assignments will be
parsed right before default_pre.prf
-beforeAll subsequent variable assignments will be
parsed right before [files] (the default)
-after All subsequent variable assignments will be
-late All subsequent variable assignments will be
parsed right after default_post.prf
-norecursive Don't do a recursive search
-recursive Do a recursive search
-set Set persistent property
-unset Unset persistent property
-query Query persistent property. Show all if is empty.
-qtconf file Use file instead of looking for qt.conf
-cache fileUse file as cache [makefile mode only]
-spec spec Use spec as QMAKESPEC [makefile mode only]
-nocache Don't use a cache file [makefile mode only]
-nodepend Don't generate dependencies [makefile mode only]
-nomoc Don't generate moc targets [makefile mode only]
-nopwd Don't look for files in pwd [project mode only]
*** Error code 1
Stop.
make: stopped in /home/marco/devel/_freebsd/ports/databases/pgadmin4
[...]
So question is why is qmake not working? Probably need to add something in
the Makefile but I've no idea what. I've tried all th
Re: how to enforce one version of python
Robert Huff writes:
> Daniel Nebdal writes:
>
>>
>> The fun
>> part is the combination of 2-only holdouts and new 3-only code,
>> which is why it's easy to end up with both installed.
>
> _This_ is really annoying. I try to keep my systems with exactly
> what they need installed, to reduce both bloat and possibly security
> issues. There's one Perl installation; having two Python versions -
> and trying to keep track between them - makes me use a lot of bad
> language.
Did you know www/firefox requires *both* Python versions to build? ;)
Mk/bsd.gecko.mk:
USES+=... python:2.7,build ...
.if ${MOZILLA_VER:R:R} >= 61
BUILD_DEPENDS+=
${LOCALBASE}/bin/python${PYTHON3_DEFAULT}:lang/python${PYTHON3_DEFAULT:S/.//g}
MOZ_EXPORT+= PYTHON3="${LOCALBASE}/bin/python${PYTHON3_DEFAULT}"
.endif
https://www.mail-archive.com/dev-platform@lists.mozilla.org/msg24187.html
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: how to enforce one version of python
Daniel Nebdal writes: > > The fun > part is the combination of 2-only holdouts and new 3-only code, > which is why it's easy to end up with both installed. _This_ is really annoying. I try to keep my systems with exactly what they need installed, to reduce both bloat and possibly security issues. There's one Perl installation; having two Python versions - and trying to keep track between them - makes me use a lot of bad language. Peevishly, Robert Huff ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: how to enforce one version of python
On Wed, 12 Sep 2018 at 19:35, tech-lists wrote: > > On 12/09/2018 13:33, Robert Huff wrote: > > How many ports_require_ python 3? > > How many ports_require_ python 2? > > yeah, I'd like to know too. I mean, I've never installed python as like > requiring it to program - it's installed as a dependency of other stuff > I want to actually run. And I thought python2 and 3 are actually > different languages rather than simply versions. Might be wrong though. > > tjhanks, > > -- > J. They are kind of both, which is both a blessing and a curse. With a bit of care you can write code that's legal in both, and even if you don't, the automatic 2to3 converter is often good enough. Thus, many packages support being configured for either version from the same source, which is why it's kind of a compile-time decision. The fun part is the combination of 2-only holdouts and new 3-only code, which is why it's easy to end up with both installed. At least there's a definite sunset for 2, so it will _eventually_ work itself out. -- Daniel Nebdal ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ databases/pgFormatter | 3.0 | v3.1 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
