On 01/06/16 17:25, Stuart Henderson wrote:
It seems the library does still get linked to system qt4 if present
(make port-lib-depends-check) - this doesn't seem quite correct but now
that the runtime warnings are gone and things seem to be working I'd
like to get this in, so I'm going to commit
After more testing and polishing I've come up with the attached patch.
It's a full diff to -current that incorporates the fixes from Stuart
as well as the ONLY_FOR_ARCH=amd64 proposed by Landry.
I believe that only the icui18n problem is left:
> On Sun, Jan 03, 2016 at 06:01:33PM +, Stuart
On Sun, Jan 03, 2016 at 06:01:33PM +, Stuart Henderson wrote:
> On 2016/01/03 17:40, Stuart Henderson wrote:
> > Here's a diff that's updated for -current. It also provides a meaningful
> > distfile name for the patched Qt, and adds DPB markers to build on multiple
> > CPUs and avoid junking
On 2016/01/03 17:40, Stuart Henderson wrote:
> On 2015/12/30 23:03, Frank Groeneveld wrote:
> > On 12/27/15 14:21, Frank Groeneveld wrote:
> > >I fixed the final problem, attached a complete diff to -current. The
> > >build takes quite a while (due to the custom qt4). On my system 125
> >
On 2015/12/30 23:03, Frank Groeneveld wrote:
> On 12/27/15 14:21, Frank Groeneveld wrote:
> >I fixed the final problem, attached a complete diff to -current. The
> >build takes quite a while (due to the custom qt4). On my system 125
> >minutes. If nobody has any objections, could somebody then
On Sun, Jan 03, 2016 at 05:40:58PM +, Stuart Henderson wrote:
> On 2015/12/30 23:03, Frank Groeneveld wrote:
> > On 12/27/15 14:21, Frank Groeneveld wrote:
> > >I fixed the final problem, attached a complete diff to -current. The
> > >build takes quite a while (due to the custom qt4). On my
On 12/27/15 14:21, Frank Groeneveld wrote:
I fixed the final problem, attached a complete diff to -current. The
build takes quite a while (due to the custom qt4). On my system 125
minutes. If nobody has any objections, could somebody then commit it for
me?
Would somebody be able to test this?
On Sun, Dec 27, 2015 at 02:21:45PM +0100, Frank Groeneveld wrote:
> On 12/17/15 01:07, Stuart Henderson wrote:
> >Check the -L flags - the path to the build directory containing the newly
> >built Qt library will need to be listed before -L/usr/local/lib. I'm not
> >sure how you'd go about passing
On 12/27/15 18:24, Landry Breuil wrote:
I think you forgot to cvs add those...
Landry
Indeed, sorry. Attached the full diff with those files added.
Frank
Index: Makefile
===
RCS file: /cvs/ports/textproc/wkhtmltopdf/Makefile,v
On 12/17/15 01:07, Stuart Henderson wrote:
Check the -L flags - the path to the build directory containing the newly
built Qt library will need to be listed before -L/usr/local/lib. I'm not
sure how you'd go about passing this in through qmake though.
I fixed the final problem, attached a
On 12/17/15 01:07, Stuart Henderson wrote:
Check the -L flags - the path to the build directory containing the newly
built Qt library will need to be listed before -L/usr/local/lib. I'm not
sure how you'd go about passing this in through qmake though.
Thanks for your hint. I should have
Attached to this email you'll find a diff that modifies the wkhtmltopdf
port so that it is statically built against their patched qt. This will
will enable the following extra features:
* Printing more then one HTML document into a PDF file.
* Running without an X11 server.
* Adding a
On 2015/12/16 22:20, Frank Groeneveld wrote:
> Attached to this email you'll find a diff that modifies the wkhtmltopdf port
> so that it is statically built against their patched qt. This will will
> enable the following extra features:
>
> * Printing more then one HTML document into a PDF file.
13 matches
Mail list logo
