EOS CDT: where are the *.h and the *.cpp files stored in the filesystem, I need reference to them to compile
I'm trying to use the EOS CDT (contract development toolkit).
I've downloaded and installed the repository from github, and used to following commands, as indicated from the eos.io development page.
https://developers.eos.io/eosio-home/docs/installing-the-contract-development-toolkit
console commands:
wget https://github.com/eosio/eosio.cdt/releases/download/v1.3.2/eosio.cdt-1.3.2.x86_64.deb
sudo apt install ./eosio.cdt-1.3.2.x86_64.deb
I can't find the reference to the h and cpp files in ubuntut's (16.04.5) filesystem.
Where are they?
I need to reference them for compiling the test codes and the examples.
I'm also using visual studio code ide.
c++ ubuntu smartcontracts eos
add a comment |
I'm trying to use the EOS CDT (contract development toolkit).
I've downloaded and installed the repository from github, and used to following commands, as indicated from the eos.io development page.
https://developers.eos.io/eosio-home/docs/installing-the-contract-development-toolkit
console commands:
wget https://github.com/eosio/eosio.cdt/releases/download/v1.3.2/eosio.cdt-1.3.2.x86_64.deb
sudo apt install ./eosio.cdt-1.3.2.x86_64.deb
I can't find the reference to the h and cpp files in ubuntut's (16.04.5) filesystem.
Where are they?
I need to reference them for compiling the test codes and the examples.
I'm also using visual studio code ide.
c++ ubuntu smartcontracts eos
Have you looked at the paths that are indicated by the link you sent /usr/local/include/eosiolib/ Was apt install successful?
– Matthieu Brucher
Nov 14 '18 at 11:53
@MatthieuBrucher Yes, the install was successful, I did not see any error message. I've looked in the /usr/local/include/ path but "eosiolib" is missing
– Luther
Nov 14 '18 at 11:56
Well, that's the location said they should be, so you should ask EOS directly!
– Matthieu Brucher
Nov 14 '18 at 12:02
1
Unless the debian file is really special, you can see which files it contains (and thus installs to your filesystem) withdpkg -c eosio.cdt-1.3.2.x86_64.deb
– Botje
Nov 14 '18 at 12:19
@Botje thanks, the CDT files are stored in /usr/opt/eosio.cdt/
– Luther
Nov 14 '18 at 12:36
add a comment |
I'm trying to use the EOS CDT (contract development toolkit).
I've downloaded and installed the repository from github, and used to following commands, as indicated from the eos.io development page.
https://developers.eos.io/eosio-home/docs/installing-the-contract-development-toolkit
console commands:
wget https://github.com/eosio/eosio.cdt/releases/download/v1.3.2/eosio.cdt-1.3.2.x86_64.deb
sudo apt install ./eosio.cdt-1.3.2.x86_64.deb
I can't find the reference to the h and cpp files in ubuntut's (16.04.5) filesystem.
Where are they?
I need to reference them for compiling the test codes and the examples.
I'm also using visual studio code ide.
c++ ubuntu smartcontracts eos
I'm trying to use the EOS CDT (contract development toolkit).
I've downloaded and installed the repository from github, and used to following commands, as indicated from the eos.io development page.
https://developers.eos.io/eosio-home/docs/installing-the-contract-development-toolkit
console commands:
wget https://github.com/eosio/eosio.cdt/releases/download/v1.3.2/eosio.cdt-1.3.2.x86_64.deb
sudo apt install ./eosio.cdt-1.3.2.x86_64.deb
I can't find the reference to the h and cpp files in ubuntut's (16.04.5) filesystem.
Where are they?
I need to reference them for compiling the test codes and the examples.
I'm also using visual studio code ide.
c++ ubuntu smartcontracts eos
c++ ubuntu smartcontracts eos
asked Nov 14 '18 at 11:49
LutherLuther
78852452
78852452
Have you looked at the paths that are indicated by the link you sent /usr/local/include/eosiolib/ Was apt install successful?
– Matthieu Brucher
Nov 14 '18 at 11:53
@MatthieuBrucher Yes, the install was successful, I did not see any error message. I've looked in the /usr/local/include/ path but "eosiolib" is missing
– Luther
Nov 14 '18 at 11:56
Well, that's the location said they should be, so you should ask EOS directly!
– Matthieu Brucher
Nov 14 '18 at 12:02
1
Unless the debian file is really special, you can see which files it contains (and thus installs to your filesystem) withdpkg -c eosio.cdt-1.3.2.x86_64.deb
– Botje
Nov 14 '18 at 12:19
@Botje thanks, the CDT files are stored in /usr/opt/eosio.cdt/
– Luther
Nov 14 '18 at 12:36
add a comment |
Have you looked at the paths that are indicated by the link you sent /usr/local/include/eosiolib/ Was apt install successful?
– Matthieu Brucher
Nov 14 '18 at 11:53
@MatthieuBrucher Yes, the install was successful, I did not see any error message. I've looked in the /usr/local/include/ path but "eosiolib" is missing
– Luther
Nov 14 '18 at 11:56
Well, that's the location said they should be, so you should ask EOS directly!
– Matthieu Brucher
Nov 14 '18 at 12:02
1
Unless the debian file is really special, you can see which files it contains (and thus installs to your filesystem) withdpkg -c eosio.cdt-1.3.2.x86_64.deb
– Botje
Nov 14 '18 at 12:19
@Botje thanks, the CDT files are stored in /usr/opt/eosio.cdt/
– Luther
Nov 14 '18 at 12:36
Have you looked at the paths that are indicated by the link you sent /usr/local/include/eosiolib/ Was apt install successful?
– Matthieu Brucher
Nov 14 '18 at 11:53
Have you looked at the paths that are indicated by the link you sent /usr/local/include/eosiolib/ Was apt install successful?
– Matthieu Brucher
Nov 14 '18 at 11:53
@MatthieuBrucher Yes, the install was successful, I did not see any error message. I've looked in the /usr/local/include/ path but "eosiolib" is missing
– Luther
Nov 14 '18 at 11:56
@MatthieuBrucher Yes, the install was successful, I did not see any error message. I've looked in the /usr/local/include/ path but "eosiolib" is missing
– Luther
Nov 14 '18 at 11:56
Well, that's the location said they should be, so you should ask EOS directly!
– Matthieu Brucher
Nov 14 '18 at 12:02
Well, that's the location said they should be, so you should ask EOS directly!
– Matthieu Brucher
Nov 14 '18 at 12:02
1
1
Unless the debian file is really special, you can see which files it contains (and thus installs to your filesystem) with
dpkg -c eosio.cdt-1.3.2.x86_64.deb
– Botje
Nov 14 '18 at 12:19
Unless the debian file is really special, you can see which files it contains (and thus installs to your filesystem) with
dpkg -c eosio.cdt-1.3.2.x86_64.deb
– Botje
Nov 14 '18 at 12:19
@Botje thanks, the CDT files are stored in /usr/opt/eosio.cdt/
– Luther
Nov 14 '18 at 12:36
@Botje thanks, the CDT files are stored in /usr/opt/eosio.cdt/
– Luther
Nov 14 '18 at 12:36
add a comment |
2 Answers
2
active
oldest
votes
Based on Botje's comment:
"Unless the debian file is really special, you can see which files it contains (and thus installs to your filesystem) with dpkg -c eosio.cdt-1.3.2.x86_64.deb"
using the command:
dpkg -c eosio.cdt-1.3.2.x86_64.deb
The folder where the files are installed are shown:
The CDT files are stored in /usr/opt/eosio.cdt/
add a comment |
For MacOS users reference, when installing with Brew include paths are located at
/usr/local/Cellar/eosio.cdt/1.4.1/opt/eosio.cdt/include/
(Please use your own version instead of 1.4.1 if applicable)
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53299568%2feos-cdt-where-are-the-h-and-the-cpp-files-stored-in-the-filesystem-i-need%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Based on Botje's comment:
"Unless the debian file is really special, you can see which files it contains (and thus installs to your filesystem) with dpkg -c eosio.cdt-1.3.2.x86_64.deb"
using the command:
dpkg -c eosio.cdt-1.3.2.x86_64.deb
The folder where the files are installed are shown:
The CDT files are stored in /usr/opt/eosio.cdt/
add a comment |
Based on Botje's comment:
"Unless the debian file is really special, you can see which files it contains (and thus installs to your filesystem) with dpkg -c eosio.cdt-1.3.2.x86_64.deb"
using the command:
dpkg -c eosio.cdt-1.3.2.x86_64.deb
The folder where the files are installed are shown:
The CDT files are stored in /usr/opt/eosio.cdt/
add a comment |
Based on Botje's comment:
"Unless the debian file is really special, you can see which files it contains (and thus installs to your filesystem) with dpkg -c eosio.cdt-1.3.2.x86_64.deb"
using the command:
dpkg -c eosio.cdt-1.3.2.x86_64.deb
The folder where the files are installed are shown:
The CDT files are stored in /usr/opt/eosio.cdt/
Based on Botje's comment:
"Unless the debian file is really special, you can see which files it contains (and thus installs to your filesystem) with dpkg -c eosio.cdt-1.3.2.x86_64.deb"
using the command:
dpkg -c eosio.cdt-1.3.2.x86_64.deb
The folder where the files are installed are shown:
The CDT files are stored in /usr/opt/eosio.cdt/
answered Nov 14 '18 at 12:40
LutherLuther
78852452
78852452
add a comment |
add a comment |
For MacOS users reference, when installing with Brew include paths are located at
/usr/local/Cellar/eosio.cdt/1.4.1/opt/eosio.cdt/include/
(Please use your own version instead of 1.4.1 if applicable)
add a comment |
For MacOS users reference, when installing with Brew include paths are located at
/usr/local/Cellar/eosio.cdt/1.4.1/opt/eosio.cdt/include/
(Please use your own version instead of 1.4.1 if applicable)
add a comment |
For MacOS users reference, when installing with Brew include paths are located at
/usr/local/Cellar/eosio.cdt/1.4.1/opt/eosio.cdt/include/
(Please use your own version instead of 1.4.1 if applicable)
For MacOS users reference, when installing with Brew include paths are located at
/usr/local/Cellar/eosio.cdt/1.4.1/opt/eosio.cdt/include/
(Please use your own version instead of 1.4.1 if applicable)
answered Nov 23 '18 at 9:46
LonklyLonkly
1,2261520
1,2261520
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53299568%2feos-cdt-where-are-the-h-and-the-cpp-files-stored-in-the-filesystem-i-need%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you looked at the paths that are indicated by the link you sent /usr/local/include/eosiolib/ Was apt install successful?
– Matthieu Brucher
Nov 14 '18 at 11:53
@MatthieuBrucher Yes, the install was successful, I did not see any error message. I've looked in the /usr/local/include/ path but "eosiolib" is missing
– Luther
Nov 14 '18 at 11:56
Well, that's the location said they should be, so you should ask EOS directly!
– Matthieu Brucher
Nov 14 '18 at 12:02
1
Unless the debian file is really special, you can see which files it contains (and thus installs to your filesystem) with
dpkg -c eosio.cdt-1.3.2.x86_64.deb
– Botje
Nov 14 '18 at 12:19
@Botje thanks, the CDT files are stored in /usr/opt/eosio.cdt/
– Luther
Nov 14 '18 at 12:36