Closed hadim closed 4 years ago
ping @aalhossary
Dear Hadrien Mary, I guess you are using the master branch. This will produce AutoDock Vina.
Please consider switching to either branches, as in these pages: https://qvina.github.io/compilingQvina2.html https://qvina.github.io/compilingQvina-w.html
Please don’t hesitate to contact me for any further inquiries.
Regards
Amr
From: Hadrien Mary notifications@github.com Sent: Friday, March 13, 2020 7:53 AM To: QVina/qvina qvina@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [QVina/qvina] Clarification about uploaded binaries (#6)
It's not clear from where the uploaded binaries in bin/ come from.
In the makefile, there is two targets all: vina vina_split which I guess corresponds to the binaries in bin/ ?
From where do the other binaries come from?
It would be helpful to have a consolidated repo where every binary each generate using a single Makefile or using CMake for example. I am happy to submit a PR if someone can provide me some guidance.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/QVina/qvina/issues/6, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA35TI4UDCYGBV2G3RQ2QHDRHFYUTANCNFSM4LGXPZWA.
Thank you for your answer. Here is a proposal to reorganize the code: https://github.com/QVina/qvina/pull/7
It's not clear from where the uploaded binaries in
bin/
come from.In the makefile, there is two targets
all: vina vina_split
which I guess corresponds to the binaries inbin/
?From where do the other binaries come from?
It would be helpful to have a consolidated repo where every binary each generate using a single Makefile or using CMake for example. I am happy to submit a PR if someone can provide me some guidance.