[Bug] Flatsharp can't compile schemas on seperate drives about flatsharp

[jamescourtney]

Fixed in 7.2.1, which uses a custom build of flatc :)

[jamescourtney]

Agree completely. You've actually inspired me to see if I can get flatc to add a drive letter to the relative path.

[OptoCloud]

Yeah, looks to be working fine 😄
Thanks! 😁

[jamescourtney]

This is a known issue. Unfortunately, there is little I can do about it.

FlatSharp uses the paths generated by flatc internally. These paths are all relative, and on Windows they do not include the drive letter. An example of a real path that flatc produces is this:

//../../../:/git/FlatSharp/test.fbs

Unfortunately, the drive letter is not present, so FlatSharp can only make guesses about the location of the file. It looks like you've contributed to google/flatbuffers before. One thing that would allow me to effectively mitigate this would be an option to add absolute paths to bfbs output instead of relative.

[OptoCloud]

Ah I see... But that would probably break backwards compatibility, so I'm guessing they won't implement that.
I can see if I find some way to have the nuget packages cached on the same drive as the source code.
Thanks for the quick answer! 😄

[OptoCloud]

Would be nice to have some kind of detection for seperate drives and give a better exception message tho 🤔

[jamescourtney]

@OptoCloud -- is this working for you now?