 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hiho,
8 years ago, in my POV-Ray 3.1 days, I used to use
#include "../../ttCommon/file.inc"
I now need to rerender my animations as 1920x1080. :) :)
I notice that I can do "../file.inc" but I can't do "../../file.inc".
I have turned off Script I/O restrictions.
The exact error is:
"C:\pov\dev\ttfo\haus\fishtank\fishtank.inc" line 96: Parse Error: Cannot open
include file ../../splineColefax.inc.
I am using 3.7.0.RC3.msvc9.win64
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 13/02/2011 16:49, dickbalaska wrote:
> Hiho,
> 8 years ago, in my POV-Ray 3.1 days, I used to use
> #include "../../ttCommon/file.inc"
> I now need to rerender my animations as 1920x1080. :) :)
> I notice that I can do "../file.inc" but I can't do "../../file.inc".
> I have turned off Script I/O restrictions.
> The exact error is:
> "C:\pov\dev\ttfo\haus\fishtank\fishtank.inc" line 96: Parse Error: Cannot open
> include file ../../splineColefax.inc.
Hi Dick,
Good to hear from you after all these years.
I can't say exactly what the cause is as I don't know your full dir layout.
Since the windows version of POV changes the current working directory to
that containing the scene or INI file, any relative file references will be
based on that location, not the directory that an included file is in. If
the failure is not related to this then I'll need to look into it further.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
dickbalaska wrote:
> Hiho,
Hey, I thought I knew your name but not from
raytracing ... now I remember: XpilotNT! ;)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason <del### [at] deletethistoo povrayorg> wrote:
> Hi Dick,
>
> Good to hear from you after all these years.
>
> I can't say exactly what the cause is as I don't know your full dir layout.
> Since the windows version of POV changes the current working directory to
> that containing the scene or INI file, any relative file references will be
> based on that location, not the directory that an included file is in. If
> the failure is not related to this then I'll need to look into it further.
>
> -- Chris
Hi Chris!
Well, it's just a standard tree...
- ttfo + ttfo.pov
|
+ haus --+ haus.inc
| + kitchen + cabinets.inc
| | - kitchen.inc
| |
| - fishtank + fishtank.inc
| - fish1.inc
|
- ttCommon + mainDecls.inc
- splineColefax.inc
A full render starts at ttfo.pov. This still works on 3.7 because everything is
tree'd below the root directory. But to develop the fishtank, I render
fishtank.inc and have to go up a few levels to get to the includes.
I manage the includes like this
#declare ttCommonDir="../../ttCommon/"
#include concat(ttCommonDir, "splineColefax.inc")
so depending on which (development) directory I am rendering from, I change the
"#declare ttCommonDir" and everybody can be found.
I have reduced the problem to; while rendering fishtank.inc, I can copy
splineColefax.inc to haus and reference it as #include "../splineColefax.inc"
but I can not copy it to ttfo and reference it as
#include "../../splineColefax.inc" .
dik
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"dickbalaska" <dic### [at] buckosoftcom> schreef in bericht
news:web.4d5770f774dbb447abf458e40@news.povray.org...
> Hiho,
> 8 years ago, in my POV-Ray 3.1 days, I used to use
> #include "../../ttCommon/file.inc"
> I now need to rerender my animations as 1920x1080. :) :)
> I notice that I can do "../file.inc" but I can't do "../../file.inc".
> I have turned off Script I/O restrictions.
> The exact error is:
> "C:\pov\dev\ttfo\haus\fishtank\fishtank.inc" line 96: Parse Error: Cannot
> open
> include file ../../splineColefax.inc.
>
Shouldn't that be: #include "..\..\ttCommon\file.inc" ? with back slashes
?
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thomas de Groot" <tDOTdegroot@interDOTnlANOTHERDOTnet> wrote:
>
> Shouldn't that be: #include "..\..\ttCommon\file.inc" ? with back slashes
> ?
>
> Thomas
I render on Linux as well as Windows. Slashes are portable (except at the DOS
command prompt).
dik
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Chris Cason<del### [at] deletethistoopovrayorg> wrote:
>> Hi Dick,
>>
>> Good to hear from you after all these years.
>>
>> I can't say exactly what the cause is as I don't know your full dir layout.
>> Since the windows version of POV changes the current working directory to
>> that containing the scene or INI file, any relative file references will be
>> based on that location, not the directory that an included file is in. If
>> the failure is not related to this then I'll need to look into it further.
>>
>> -- Chris
>
> Hi Chris!
>
> Well, it's just a standard tree...
> - ttfo + ttfo.pov
> |
> + haus --+ haus.inc
> | + kitchen + cabinets.inc
> | | - kitchen.inc
> | |
> | - fishtank + fishtank.inc
> | - fish1.inc
> |
> - ttCommon + mainDecls.inc
> - splineColefax.inc
>
> A full render starts at ttfo.pov. This still works on 3.7 because everything is
> tree'd below the root directory. But to develop the fishtank, I render
> fishtank.inc and have to go up a few levels to get to the includes.
>
> I manage the includes like this
> #declare ttCommonDir="../../ttCommon/"
> #include concat(ttCommonDir, "splineColefax.inc")
>
> so depending on which (development) directory I am rendering from, I change the
> "#declare ttCommonDir" and everybody can be found.
>
> I have reduced the problem to; while rendering fishtank.inc, I can copy
> splineColefax.inc to haus and reference it as #include "../splineColefax.inc"
> but I can not copy it to ttfo and reference it as
> #include "../../splineColefax.inc" .
>
> dik
>
>
>
>
>
In your place, I'd place splineColefax.inc in the common include folder.
That way, it's available for any of your scene.
General tip:
Place general library include files in the include folder and only place
scene specific includes in the file's folder.
Alain
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have uploaded a small test to the binary scene-files.
It demonstrates that I can not include "../../file0.pov"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 15.02.2011 05:54, schrieb dickbalaska:
> I have uploaded a small test to the binary scene-files.
> It demonstrates that I can not include "../../file0.pov"
Found the bastard! Definite bug - when parsing a file path, POV-Ray
attempts to eliminate ".." by stripping the preceding component from the
path - e.g. "foo/bar/../something" becomes "foo/something";
unfortunately, it does this even if the previous element happens to be
".." as well. So "../../file0.pov" simply becomes "file0.pov".
FAIL.
I'll go fix that. Dick, would you mind entering a report on
http://bugs.povray.org in the meantime, so this gets listed as a known bug?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 16.02.11 03:26, clipka wrote:
> Am 15.02.2011 05:54, schrieb dickbalaska:
>> I have uploaded a small test to the binary scene-files.
>> It demonstrates that I can not include "../../file0.pov"
>
> Found the bastard! Definite bug - when parsing a file path, POV-Ray attempts
> to eliminate ".." by stripping the preceding component from the path - e.g.
> "foo/bar/../something" becomes "foo/something"; unfortunately, it does this
> even if the previous element happens to be ".." as well. So
> "../../file0.pov" simply becomes "file0.pov".
>
> FAIL.
>
> I'll go fix that. Dick, would you mind entering a report on
> http://bugs.povray.org in the meantime, so this gets listed as a known bug?
STOP, that is no bug, that is by design!
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
