start from a clean slate of MUQ and make sure things work and we are able to build things without hiccups, which i think is the current status
complete #11 : this gives us an idea of what dependencies each target has
delete/remove all uses of MUQ_LINK_LIBS and similar: this is intentional, because by doing this we modify the code so that it should NOT compile anymore. this is what we want. However, when we do this we should NOT delete parts of the code dealing with compile groups. That should stay.
for each target of MUQ (starting from the sampling component as dicussed with Dakota team), start adding things (find_package with namespacing linking, etc) and fix things so that it compiles and works again. WHILE doing this, we can simplify existing code if needed.
First, we should do this successfully for the case when all TPLs are externally found
then, we verify that this works properly if a TPL is built internally
If we follow this process, I think we should be able to complete most of the work for task 1.
fnrizzi
commented
3 weeks ago
I think that we should try to follow these steps:
start from a clean slate of MUQ and make sure things work and we are able to build things without hiccups, which i think is the current status
complete #11 : this gives us an idea of what dependencies each target has
delete/remove all uses of
MUQ_LINK_LIBSand similar: this is intentional, because by doing this we modify the code so that it should NOT compile anymore. this is what we want. However, when we do this we should NOT delete parts of the code dealing with compile groups. That should stay.for each target of MUQ (starting from the sampling component as dicussed with Dakota team), start adding things (find_package with namespacing linking, etc) and fix things so that it compiles and works again. WHILE doing this, we can simplify existing code if needed.
If we follow this process, I think we should be able to complete most of the work for task 1.