On 07/17/2017 23:33, Klaus T. Aehlig wrote:
Actually, it is not that far in the future; in fact, event today, bazel's
cc_library rule accepts an .so in the sources attribute, making a work around
possible (patching WORKSPACE to point to a hand-crafted directory under WRKDIR
as a local_repository,
On Mon, Jul 17, 2017 at 09:37:34AM +0200, Klaus T. Aehlig wrote:
> However, even with that approach, you should be aware that you're
> embedding the relevant dependencies rather than using them from
> ${LOCALBASE}. So, in the long run, it might be desirable to patch the
> relevant targets in the BU
from Franco Fichtner:
# pkg repo /mnt/usr/packages
Would that put meta.txz and other stuff in /usr/packages ?
I could do that either by nfs (with /mnt) or directly on that computer (without
/mnt).
But I have all the old stuff I no longer want, would not run because of shared
libraries out of
On Monday, 17 July 2017 at 15:58:05 -0700, David P. Discher wrote:
> There is a new version of the nvidia driver on there site as of may 9th ???
>
> Version: 381.22
> Release Date: 2017.5.9
>
> This Added support for GeForce GT 1030 ??? which I???d imagine
> others may start trying to use l
Yuri writes:
> On 07/17/2017 15:18, Jan Beich wrote:
>
>> Do you mean something like the following?
>>
>>Generating MOC compilation qtox_autogen/moc_compilation.cpp
>>[...]
>>Generating MOC source qtox_static_autogen/44CYS2DDJC/moc_openal.cpp
>
>
> On linux it prints "Automatic moc fo
There is a new version of the nvidia driver on there site as of may 9th …
Version: 381.22
Release Date: 2017.5.9
This Added support for GeForce GT 1030 … which I’d imagine others may start
trying to use like myself. This older driver doesn’t work at all with the 1030.
--
David P. Dis
On 07/17/2017 15:18, Jan Beich wrote:
Do you mean something like the following?
Generating MOC compilation qtox_autogen/moc_compilation.cpp
[...]
Generating MOC source qtox_static_autogen/44CYS2DDJC/moc_openal.cpp
On linux it prints "Automatic moc for target", like here:
https://gis
On 07/17/2017 13:54, Yuri wrote:
net-im/qTox fails to build. It uses Qt5, has set(CMAKE_AUTOMOC ON) in
CMakeFiles.txt but moc isn't called.
I created the bug report:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220811
Yuri
___
freebsd-port
Yuri writes:
> On 07/17/2017 14:21, Jan Beich wrote:
>
>> Can you show the error log? IIRC, CMake cannot build Qt-based projects
>> without QMake installed and automoc isn't invoked for Qt5.
>>
>> I maintain a few Qt5 ports that build via USES=cmake. For one,
>> citra-qt5, ppsspp-qt5, rpcs3 have
On 07/17/2017 14:21, Jan Beich wrote:
Can you show the error log? IIRC, CMake cannot build Qt-based projects
without QMake installed and automoc isn't invoked for Qt5.
I maintain a few Qt5 ports that build via USES=cmake. For one,
citra-qt5, ppsspp-qt5, rpcs3 have set(CMAKE_AUTOMOC ON).
Addin
Yuri writes:
> On 07/17/2017 13:59, Jan Beich wrote:
>
>> Did you try USE_QT5=qmake_build ?
>
>
> They got rid of qmake, they use only cmake. Apparently,
> cmake+CMAKE_AUTOMOC without qmake works on linux.
Can you show the error log? IIRC, CMake cannot build Qt-based projects
without QMake insta
On 07/17/2017 13:59, Jan Beich wrote:
Did you try USE_QT5=qmake_build ?
They got rid of qmake, they use only cmake. Apparently,
cmake+CMAKE_AUTOMOC without qmake works on linux.
Yuri
___
freebsd-ports@freebsd.org mailing list
https://lists.freeb
Yuri writes:
> net-im/qTox fails to build. It uses Qt5, has set(CMAKE_AUTOMOC ON) in
> CMakeFiles.txt but moc isn't called.
>
> On Linux there is a separate automoc package.
>
> FreeBSD has automoc4, but not automoc5.
>
> Shouldn't there be automoc5? What might be wrong?
>
>
> USE_QT5=cor
net-im/qTox fails to build. It uses Qt5, has set(CMAKE_AUTOMOC ON) in
CMakeFiles.txt but moc isn't called.
On Linux there is a separate automoc package.
FreeBSD has automoc4, but not automoc5.
Shouldn't there be automoc5? What might be wrong?
USE_QT5=core gui network xml opengl sql s
> On 17 Jul, 2017, at 11:13, Patrick Powell wrote:
>
> On 07/16/17 22:21, Matthias Apitz wrote:
>> El día lunes, julio 17, 2017 a las 05:10:06a. m. +, Thomas Mueller
>> escribió:
>>
>>> How do I get pkg to recognize a local repository such as
>>> /mnt/usr/packages/All, or does pkg only rec
Hi!
> Just out of curiosity (and because I might want to do this) how can you
> specify two (or more) repositories
> and have them searched in some order.
Probably by having two or more config files for repos in
/usr/local/etc/pkg/repos/
I don't know how to have preferences in there.
--
p...
On 07/16/17 22:21, Matthias Apitz wrote:
El día lunes, julio 17, 2017 a las 05:10:06a. m. +, Thomas Mueller escribió:
How do I get pkg to recognize a local repository such as /mnt/usr/packages/All,
or does pkg only recognize remote repositories?
...
I use:
$ ls -l /usr/local/etc/pkg/rep
On 15.07.2017 08:54, Jonathan Chen wrote:
> In particular, the LIB_DEPENDS entry "libelf.so:devel/libelf" is
> causing the confusion. On my 11-STABLE/amd64 host, this is included in
> the base system (/usr/lib/libelf.so); but since it is listed in
> LIB_DEPENDS, synth gets confused as to why the p
On 16/07/2017 20:54, Grzegorz Junka wrote:
On 16/07/2017 13:35, Kurt Jaeger wrote:
Hi!
Hmm, I found this:
pkg clean -a
cleans the cache and
pkg install -R -f firefox
should force a reinstallation of the package and all dependencies.
Well, indeed, as you posted already, it does not 8-(
Hi Thomas,
17.07.2017 08:10, Thomas Mueller пишет:
How do I get pkg to recognize a local repository
It is documented at PKG-REPOSITORY(5) . [1]
What is the proper URL or format for a file name/directory? Is it necessary to
precede with URL: or what do I have to do to make it look like a
> Bazel (devel/bazel) based projects tend to fetch tarballs directly.
> WORKSPACE can be patched to change the fetch URL to one in
> /usr/ports/distfiles. However, what to do when the contents of tarballs
> need to be patched?
Unfortunately, there is no real good bazel way to do this. It was
di
21 matches
Mail list logo
