-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…
-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…
-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…
-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…
-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…
-
```
Apple build fails.
In line 288 of CMakeList.txt WORK_DIR is being set null from
CMAKE_RUNTIME_OUTPUT_DIRECTORY
I used: SET( WORK_DIR "${CMAKE_SOURCE_DIR}")
Mac OSX 10.7.2, macports qt4.7.4
…
-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…
-
Running the `lbuild` script using the following `project.xml`:
``` xml
:ws2812
```
results in this error:
```
$ ../library-builder/scripts/lbuild -r ../loa-hdl/loa-hdl.lb -c…
-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…
-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…