Patrick Quist

When using the default target it also reveals this issue https://github.com/compiler-explorer/compiler-explorer/issues/1206 as we do not have the required headers for these targets. Related issue is also https://github.com/compiler-explorer/compiler-explorer/issues/3868

This has been blocked for a while because of issues I encountered during my attempt to add this to CE. I however do not remember what those issues were at...

I remembered this request again and just had a quick try, as we have better tools on supporting libraries nowadays. I built the master branch and it produced `libCsCore1.7.so`, `libCsNetwork1.7.so`,...

Perhaps it doesn't have to be so complicated if there was to be a cmake target/defines to only generate the include folder. Would that be possible @janwilmans ?

> I'm not sure what you mean with 'only generate the include folder', copperspice is not a header only library, so a bunch of .so files are needed at runtime....

> Ah, I understand a bit more now. Would it help if I offer the pre-build result in a separate repo ? That would also be an option, but it...

Sure that might work

> this being said, to actually run the program, I guess you _do_ need to .so's to be present, for what environment should they be build ? We pre-build for...

I don't really understand why rust doesn't do this by default itself when a certain "edition" is stable enough. With C++ the compiler vendors update the default Standard C++ version...

> I believe the idea is that changing the default edition is considered a breaking change, which violates Rust’s stability guarantee. > > Relevant comment in the original editions RFC:...