On Sat, Jul 26, 2008 at 3:25 AM, <[EMAIL PROTECTED]> wrote:
> >Hi,
> >
> >I am using CS 1.4 since CS trunk gave me rendering problems in CEL
> >applications. thebolt recommended i used CS 1.4 and that appears to work,
> at
> >least under a new installation of windows vista. Should i still merge CEL
> >trunk into my branch?
> >
> >TIA,
> >-dannyBlue
>
> Yes, since your branch is derived from CEL trunk.
> But you should really use CS trunk, not 1.4 (other than for temporary
> work-around).
> Did you retry CS trunk since that windows vista re-installation ?
> (and don't forget to rebuild CEL, or have another checkout, against that CS
> trunk)
Ok I will merge and see if the build problems get solved.
Yes I tried CS trunk with my branch, the rendering problems manifested as a
lack of lighting on the world geometry (level was rendered black).
Since the current setup works and i have wasted way too much time working
around version building, i will proceed with CS 1.4.
I need to start work on some test applications. What is the best way to
handle this sort of scenario? Add a new application to the solution or
compile it on it's own? Any guidelines on doing this?
I have tried compiling an external project (followed the tutorial on the
manual
http://www.crystalspace3d.org/docs/online/manual/HOWTO-Creating-External-MSVC-Application.html#0
)
but linking errors continued to creep up.
For the time being i am simply modifying an existing application.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Cel-main mailing list
Cel-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cel-main
