Skip to content
This repository has been archived by the owner on Dec 8, 2017. It is now read-only.

Installation process of Thirdparty binaries #4

Open
jpfeuffer opened this issue Jul 15, 2016 · 4 comments
Open

Installation process of Thirdparty binaries #4

jpfeuffer opened this issue Jul 15, 2016 · 4 comments

Comments

@jpfeuffer
Copy link
Contributor

While looking at how to exclude the Thirdparty binaries from this repo by making the path to them variable, I saw that actually all the folders are hard coded.
I.e. the Installer script installs the Fido folder, then the Xtandem folder, then the MSGF folder and so on. Since we are getting more and more thirdparty binaries it would be great to find a programmatic solution.

@jpfeuffer
Copy link
Contributor Author

In general: What do you think about putting all Thirdparty executables into one folder (AFTER copying/installing)? I know it's a bit more messy but on the other hand we would not clutter the paths all the time and makes the scripts easier.

@timosachsenberg
Copy link
Contributor

this might work right now but is general a bit dangerous as there might be different versions of e.g. runtime libraries with the same name

@timosachsenberg
Copy link
Contributor

e.g. pwiz and myrimatch

@timosachsenberg
Copy link
Contributor

timosachsenberg commented Aug 22, 2016

close?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants