Re: [Development] FreeBSD 10 and up, No gcc and solution

2015-11-18 Thread Giuseppe D'Angelo
On Wed, Nov 18, 2015 at 1:30 PM, Daniel Dettlaff  wrote:
> Under 11.x it causes clang warnings (non fatal though so I left it this way).

Maybe you can contribute your improvements to the mkspecs?
http://wiki.qt.io/Category:Developing_Qt

Cheers,

-- 
Giuseppe D'Angelo
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] FreeBSD 10 and up, No gcc and solution

2015-11-18 Thread Daniel Dettlaff
> I created a spec for freebsd-clang based on freebsd-g++46.
> It’s described/ scripted how I did create freebsd-clang spec for fBSD 10 and 
> 11 (tested with a lot of modules, and external Qt software since FreeBSD 10.0)
> Standard specs bundled by default are - freebsd-g++, freebsd-g++46 and 
> freebsd-icc - which simply wont work anymore for newer FreeBSD OS releases 
> (without gcc).

It’s also worth mentioning:

```
${SED_BIN} -i '' -e 's/-pthread/-pthread -lutil -lexecinfo/g’ qmake.conf
```

this part is necessary only under FreeBSD 10.x

Under 11.x it causes clang warnings (non fatal though so I left it this way).

--
kind regards
Daniel (dmilith) Dettlaff


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] FreeBSD 10 and up, No gcc and solution

2015-11-18 Thread Ralf Nolden
Am Mittwoch, 18. November 2015, 13:01:26 schrieb Daniel Dettlaff:

Hi Daniel,

you can simply use ./configure -platform unsupported/freebsd-clang

I've provided some patches for Qt on FreeBSD on the kde-freebsd mailinglist to 
move the libs to /usr/local/lib/qt5 which are still not in the freebsd ports 
yet. Those allow using portupgrade and building a custom Qt with a 
ports/packages installed Qt without build errors. You may want to have a look 
at those too.



> Hello, I’m heavy Qt user under FreeBSD on my servers (no gui stuff).
> 
> Here’s a definition for qt5 in my software (skip the software, it doesn’t
> matter):
> https://bitbucket.org/verknowsys/sofin-definitions/src/e57660d476d3725dc7aa
> a8a637be59da59349b22/definitions/qtbase55.def?at=stable&fileviewer=file-view
> -default
> 
> I created a spec for freebsd-clang based on freebsd-g++46.
> It’s described/ scripted how I did create freebsd-clang spec for fBSD 10 and
> 11 (tested with a lot of modules, and external Qt software since FreeBSD
> 10.0) Standard specs bundled by default are - freebsd-g++, freebsd-g++46
> and freebsd-icc - which simply wont work anymore for newer FreeBSD OS
> releases (without gcc).
> 
> My question is could you please provide such spec by default to be shipped
> with Qt itself? My solution is a hack obviously.
> 
> --
> kind regards
> Daniel (dmilith) Dettlaff

-- 
Kind regards,

Ralf Nolden

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


[Development] FreeBSD 10 and up, No gcc and solution

2015-11-18 Thread Daniel Dettlaff
Hello, I’m heavy Qt user under FreeBSD on my servers (no gui stuff).

Here’s a definition for qt5 in my software (skip the software, it doesn’t 
matter): 
https://bitbucket.org/verknowsys/sofin-definitions/src/e57660d476d3725dc7aaa8a637be59da59349b22/definitions/qtbase55.def?at=stable&fileviewer=file-view-default

I created a spec for freebsd-clang based on freebsd-g++46.
It’s described/ scripted how I did create freebsd-clang spec for fBSD 10 and 11 
(tested with a lot of modules, and external Qt software since FreeBSD 10.0)
Standard specs bundled by default are - freebsd-g++, freebsd-g++46 and 
freebsd-icc - which simply wont work anymore for newer FreeBSD OS releases 
(without gcc).

My question is could you please provide such spec by default to be shipped with 
Qt itself? My solution is a hack obviously.

--
kind regards
Daniel (dmilith) Dettlaff




signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development