External libraries installation

[vegaonline]

No description provided.

[hughcars]

Hi @vegaonline,

Could you expand on what you mean by this issue? Palace opts for the strategy of building it's dependencies internally because frequently we maintain patches for them, and requiring a user to perform the patch process and correctly build and link everything is too onerous for most. If you are looking for an alternative to the super build process, I can suggest spack which provides a packaged experience.

[vegaonline]

I need to install in an workstation which is in intranet and not in internet.

1. I ran cmake first time to get extern and other folders.
2. I checked each library folders inside the 'extern' folder to get URL to download that library and downloaded from a separate internet connected machine.
3. Now I copied each external libraries in respective folders inside 'extern' as 'extern/<library_name>-cmake/src/'.

I tried to run make now hoping that it will use the downloaded libraries instead of fresh downloading. But the installer tried to download again. I want to get advice how may I instruct cmake to use the downloaded files.

[hughcars]

Ah. That's a bit non-standard, but you can probably pull that manual build off. I think you're just copying them into the wrong directories, you need to use the url and git tags from here, then copy the resulting files into extern/<library_name> rather than extern/<library_name>-cmake/src. Once they are copied in there, I believe the build script will be ok, as it will attempt to apply the patches into those source directories, then build from there. You might have an issue if there is a git update in one of the patch builds (check the ExternalXXXX.cmake files to see the build step at the end of each), but you will have to see that for yourself.

Once that is done, I believe make in the top build directory will succeed.