Discussion related to cado-nfs

[Emmanuel Thomé <Emmanuel.Thome@inria.fr>]

Hi,

It is true that cado-nfs has a few absolute paths here and there
that are getting in the way on certain occasions.

Could you please clarify what you're trying to do that currently doesn't
work? I can't really tell what you have in your github, so it's not
entirely clear to me.
 - are you trying to move data files, such as sieving result files
   created by the las binary, to other machines for processing? That
   definitely should work.
 - are you trying to move an entire cado-nfs working directory (the one
   that gets automatically created by cado-nfs.py), along with its
   database file (the one in .db) to another machine? This probably
   doesn't work.
 - are you trying to move binaries from one machine to another? In
   principle, this should work, but it depends on the way you do it.
   (There are ways to make it fail...)

Best,

E.


On Tue, Mar 22, 2022 at 08:22:49PM -0500, Samer Najjar wrote:
> Hello cado-nfs team,
> 
> I am working on a project that uses cado-nfs and my project is uploaded to
> GitHub. The problem is that, when I run "make" in the cado-nfs directory,
> it creates files that only work locally (i.e. use local file paths). So if
> I clone my GitHub project onto another machine, the cado-nfs functionality
> would no longer work. Is there a way to make it so all the functionality in
> the cado-nfs directory works fine no matter where I move the directory?
> (i.e. is it possible to make cado-nfs independent of local file paths?)
> 
> Your help is really appreciated.
> Best,
> Samer Najjar