Possible issue in parallel builds when two file have the same name about nimibook HOT 10 CLOSED

I will try to fix this in the coming week. What I've found is that it's as easy as passing --nimcache:path to change the nimcache folder. And we can get the current nimcache folder using this code from forum thread:

import std/compilesettings
const nimcache = querySetting(SingleValueSetting.nimcacheDir)

So we just have to combine this nimcache with the relative path of the current document to get the desired results.

from nimibook.

Yes that sounds like it could work. And we would get the benefit of all the cache being intact 👍

from nimibook.

ah but you have also stuff like /home/runner/.cache/nim/index_d/@mindex.nim.c.o so that might create a conflict anyway

from nimibook.

ah but you have also stuff like /home/runner/.cache/nim/index_d/@mindex.nim.c.o so that might create a conflict anyway

Yes exactly, it's those that are the problem I think because it was the C compiler that complained about not finding references. Which would be because we have overridden some file before it was finished compiling or something like that

from nimibook.

Isn't there some compiler option that allows to override the name of file in cache? If so we could just add the index of the file in the list of file to build or something else to disambiguate

from nimibook.

I would say it depends on what -o:outputname does when using nim r as there is no non-temporary binary to save. Hopefully it uses that name as well in the cache but I'm not holding my hopes up 😬 will investigate it further tomorrow, I hope I'm wrong though.

from nimibook.

another option would be to override the Nim cache folder and replicate the folder structure of source files (+ a base folder that could be the default one)

from nimibook.

I have tried setting -o:another_name and it doesn't work sadly :/.

another option would be to override the Nim cache folder and replicate the folder structure of source files (+ a base folder that could be the default one)

I'm not really following here, what is is we should replicate?
Should we create a unique nimcache folder for each file?

from nimibook.

well if I understand correctly we have issues with a structure like this:

index.nim
section1/index.nim

because when processed concurrently nim creates c files with the same name in nimcache folder (calling it $nimcache here), like $nimcache/index.c. If instead we ask for the second index file to use as nimcache $nimcache/section1 (so that the c file is $nimcache/section1/index.c this should solve the issue, right?

from nimibook.

still, I had a brief look at the log and not entirely sure the issue is conflict of filenames:
I see a name like /home/runner/.cache/nim/index_d/index_48315C86F820572F8ADD5336011EE02A9F1B2C7F and it looks like filenames are mangled? maybe it is an issue when filenames have same name and same content?

and to be honest I have only a limited knowledge of nimcache logic...

from nimibook.