The very first released binaries of Pixie 2.2.5 were broken and installed in the wrong location, but it was quickly fixed. The current download does not install in /Applications/Graphics but in /Library/Pixie.
What error did you get when you tried compiling?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
grep: /sw/lib/libjpeg.la: No such file or directory
sed: /sw/lib/libjpeg.la: No such file or directory
libtool: link: `/sw/lib/libjpeg.la' is not a valid libtool archive
make[3]: *** [file.la] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
the "./configure" part goes ok.
That error happens with "make"
I move pixie from library to applications. I will reinstall and see what happens.
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You cannot move the installed Pixie; that's why it installs in /Library/Pixie instead of /Applications. All the binaries have built-in links to /Library/Pixie which break if you move them.
Someday there will be a native Mac frontend .app which can be moved anywhere.
You either need to put /Library/Pixie/bin in $PATH, or use the full path
$/Library/Pixie/bin/rndr ....
every time you call it.
The path errors you're getting are from Fink; you need to fix Fink before building Pixie with autoconf.
You can also build Pixie with Xcode. This requires an extra step to build the external libraries first - there are scripts in PixieLib which will download and build the required libraries. Then you can build the Pixie package in Xcode.
The "X connection..." error is due to X11. You need to start X11.app to have framebuffer display. There is currently not a native Mac framebuffer display available, but one is being worked on.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I am using Mac OsX and I get this error when I run rndr
dyld: Library not loaded: /Library/Pixie/lib/libri.dylib
Referenced from: /Applications/Graphics/Pixie/bin/rndr
Reason: image not found
Trace/BPT trap
I did not compile the software because i was getting another error.
The shader compiler is working fine. The problem is when i try to render.
Thanks in advance!
The very first released binaries of Pixie 2.2.5 were broken and installed in the wrong location, but it was quickly fixed. The current download does not install in /Applications/Graphics but in /Library/Pixie.
What error did you get when you tried compiling?
The error when try to compile is:
grep: /sw/lib/libjpeg.la: No such file or directory
sed: /sw/lib/libjpeg.la: No such file or directory
libtool: link: `/sw/lib/libjpeg.la' is not a valid libtool archive
make[3]: *** [file.la] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
the "./configure" part goes ok.
That error happens with "make"
I move pixie from library to applications. I will reinstall and see what happens.
Thanks
Well... the binary is working now!!!
I got this errors when I render the SSS shader example:
F1SB0Beauty.rib (23): Failed open environment "spotmap1.tx"
X connection to /tmp/launch-6ref8S/:0 broken (explicit kill or server shutdown).
Is that ok?
Thanks A LOT!!!
You cannot move the installed Pixie; that's why it installs in /Library/Pixie instead of /Applications. All the binaries have built-in links to /Library/Pixie which break if you move them.
Someday there will be a native Mac frontend .app which can be moved anywhere.
You either need to put /Library/Pixie/bin in $PATH, or use the full path
$/Library/Pixie/bin/rndr ....
every time you call it.
The path errors you're getting are from Fink; you need to fix Fink before building Pixie with autoconf.
You can also build Pixie with Xcode. This requires an extra step to build the external libraries first - there are scripts in PixieLib which will download and build the required libraries. Then you can build the Pixie package in Xcode.
The "X connection..." error is due to X11. You need to start X11.app to have framebuffer display. There is currently not a native Mac framebuffer display available, but one is being worked on.