forked from jl777/komodo
-
Notifications
You must be signed in to change notification settings - Fork 99
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rebuild libcc.so when dependencies change
- Loading branch information
1 parent
d3f7819
commit 62ae1c2
Showing
1 changed file
with
3 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
62ae1c2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okay,
I noticed that the libcc is created as a static lib (but given a name with .so, .dll ext) and I temporarily fixed its name as libcc.a in the tokel branch
maybe it is still a static lib in your repo
62ae1c2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will find out if my branch is using it as static or dynamic. Do you know if there a reason to make it a dynamic library?
62ae1c2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the initial intention was to make it dynamic to enable cc modules without rebuilding the whole daemon (https://developers.komodoplatform.com/basic-docs/smart-chains/smart-chain-api/cclib.html)
I did a deeper look: seems it is even not a lib but simply an object file (as it is complied with -c option)