|
 |
On 2/11/25 11:17, jr wrote:
> hi,
>
> kurtz le pirate <kur### [at] free fr> wrote:
>>
>> I think I'd have to re-run "make install" with my folder as the target,
>> but I can't see (or I didn't understand) how to do that.
>
> I too installed yuqk in a convenient place. write an email, I'd be happy to
> send you a build script and stuff.
>
>
> regards, jr.
>
The script jr uses is good. (Thanks jr).
---
I'll quickly add for others who might see this thread, for a more
permanent install you should not use the /tmp directory as I did in
examples - for safety reasons. That directory is generally deleted by
most unix/linux operating systems during the shutdown/reboot process.
Rather, create a directory somewhere under your $HOME directory where
you do (aim) your 'make install's. For example, once, in your home
directory execute the command:
mkdir yuqkBuilds
Then when you run the configuration command use:_a5c25dda
./configure -q COMPILED_BY=... --prefix=$HOME/yuqkBuilds/yuqk_a5c25dda
Later when you do 'make install' all the files will be copied for you
into that --prefix specified directory. Most important for your issue,
the 'povray' executable looks to the expected / configured install
location for that 'install-level' configuration file.
Lastly, it's very likely in using the yuqk fork, you will have multiple
versions installed so a wrapper script like 'yuqk' is the way the
'povray' executable is expected to be run / called.
All that said - there are many alternate methods to set things up. :-)
Bill P.
Post a reply to this message
|
 |