^thehatsrule^
Group: Members
Posts: 3275
Joined: July 2006 |
 |
Posted: June 10 2008,00:07 |
 |
| Quote (WDef @ June 09 2008,18:28) | Explicitly set the include path to freetype2 and then ran into the PATH_MAX error, or so I realized after tracing back through the header errors. I don't really know if it's kosher but I got around it by setting:
| Code Sample | | #define PATH_MAX 4096 /* # chars in a path name including nul */ |
at the top of the compiler.h header in the Qt4 sources.
That value is what I assume it is supposed to be from linux/limits.h, but I don't really know (or why Qt4 can't find that). |
That's a problem with the compile-3.3.5 extension.
One way around it is to do the .../include workaround (see forum thread(s) or .info)
The .info has the wrong info, actually. It has| Quote | $ cp -a /opt/compile-3.3.5/optional /opt
$ export CPPFLAGS=-I/opt/include |
while the first line should be| Quote | | $ cp -a /opt/compile-3.3.5/include /opt |
| Quote | EDIT: might be ok to just put the QtCore and QtGui libs in a uci (that is the absolute minimum I think), but there is always going to be something that comes along that won't run.
Overly obsessing about the size of ucis is absolutely pointless anyway imho, it makes no difference whatsoever, except to the download size, and to all the things that won't run or to the lost functionality of the package because some key thing has been removed. |
You could always make 2 extensions if there is a noticeable size difference (if you have time).
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
