Consolidate native code building scripts into 1 place about arcade HOT 8 CLOSED

We could add something to eng/common/

The other drawback to that approach is that repos don't get to decide where in the folder hierarchy the file needs to live. So in order for the script to be found, the calling scripts need to know where the $RepoRoot is - so they can find $RepoRoot/eng/common. There also may be files (like CMake files) that depend on being in a specific location in the folder structure.

IMO - the system should be built in such a way that files can be placed anywhere in the repo, and still be kept in sync with the 'master' script.

from arcade.

We need to make sure this change to symbol stripping gets in here: https://github.com/dotnet/core-setup/issues/1607. (Keeping unstripped binaries around even if symbol stripping is enabled, for certain scenarios where later tooling expects to do the stripping itself.)

from arcade.

A bit related to #53. We could add something to eng/common/. Drawback of this approach is that repos that don't need these files will end up with them in their repos anyway, probably not a big deal if the benefit is big

from arcade.

Maybe consider if this fits in with #774, dependency expression extensibility. That is, make the scripts a dependency repos can add if they need them, and express anywhere they want.

from arcade.

Yes I agree this should be extensible and repo's should be able to opt-in to particular folders and their locations. I was chatting with @mmitche about something similar for version updates but I think the same should hold true for file updates. Repo's can easily configure this in their Version.details.xml file.

from arcade.

Yeah that's what I'm thinking. I think we need more generic dependency expression, let me see what I can come up with.

from arcade.

@mmitche what do you want to do with this one?

from arcade.

I think we can close it. Most of the native code has been consolidated into runtime, so there is much less copying around now.

from arcade.