[ET Trac] #2834: Baikal regeneration instruction in README fail

[Roland Haas]

#2834: Baikal regeneration instruction in README fail

 Reporter: Roland Haas
   Status: new
Milestone: ET_2024_11
  Version: 
     Type: bug
 Priority: major
Component: 

Comment (by Roland Haas):

These changes are all fine and there is nothing wrong with the generated Baikal\* code updating during the release lifetime. What I am after is to have a way for the release manager and potential Baikal\* users to generate the C code from the original Python code. So that in case one has bug fixes to propose one can actually start from the real source code and not something unknown.  
  
Having the full thorn be generated with just a single command is very useful for the release manager since they have to generate very many thorns and if each one required a dozen manual steps \(worst would be “edit this file …”\), then this becomes very time consuming.  
  
The Kranc generated files uniformly require that one does `make` in the the `m` directory which contains the actual source code. RIght now with Baikal it seems that the source used is in `nrpy` and stored in some, to most users, unknown directory in `~/.local` unless one uses a virtualenv.

--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2834/baikal-regeneration-instruction-in-readme
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.einsteintoolkit.org/pipermail/trac/attachments/20241108/ece8c0c9/attachment.htm>