Getting Xcode C++ linker error when trying to run an example using Armadillo library
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am trying to run an example program (comes with installation of Armadillo library) in Xcode and getting the following error:
linker command failed with exit code -1 (use -v for invocation)
I can't figure out what's going in from Google searches.
I can build and run the program on the command prompt using:
g++ example1.cpp -O2 -larmadillo
Here's my build setting:
Here's my search path to include the armadillo.h header:
My code is:
The actual error is:
c++ xcode linker-errors armadillo
add a comment |
I am trying to run an example program (comes with installation of Armadillo library) in Xcode and getting the following error:
linker command failed with exit code -1 (use -v for invocation)
I can't figure out what's going in from Google searches.
I can build and run the program on the command prompt using:
g++ example1.cpp -O2 -larmadillo
Here's my build setting:
Here's my search path to include the armadillo.h header:
My code is:
The actual error is:
c++ xcode linker-errors armadillo
Please add the actual error message from the linker. It should be right before the output you posted. Probably your code is also required to answer the question.
– user10605163
Nov 16 '18 at 23:38
-O2 isn't a linker flag, and g++ accepts and convayes linker flags to the linker, it acts like a driver in that case. Is XCode useing clang these days? If you are using g++ in XCode the -O2 -larmadillo should be a compiler flag not a linker flag. I also assume that because it works from the shell that the library is in g++'s search paths already so unless Xcode is rewriting the entire PATH environment variable then it should be able to find it.
– johnathan
Nov 17 '18 at 0:46
I have added the code in the original posting, and also the actual error.
– Suvo
Nov 17 '18 at 10:32
I have tried building without the -O2 flag. It still provides the same error in Xcode. But I can build the code using the command prompt.
– Suvo
Nov 17 '18 at 10:50
add a comment |
I am trying to run an example program (comes with installation of Armadillo library) in Xcode and getting the following error:
linker command failed with exit code -1 (use -v for invocation)
I can't figure out what's going in from Google searches.
I can build and run the program on the command prompt using:
g++ example1.cpp -O2 -larmadillo
Here's my build setting:
Here's my search path to include the armadillo.h header:
My code is:
The actual error is:
c++ xcode linker-errors armadillo
I am trying to run an example program (comes with installation of Armadillo library) in Xcode and getting the following error:
linker command failed with exit code -1 (use -v for invocation)
I can't figure out what's going in from Google searches.
I can build and run the program on the command prompt using:
g++ example1.cpp -O2 -larmadillo
Here's my build setting:
Here's my search path to include the armadillo.h header:
My code is:
The actual error is:
c++ xcode linker-errors armadillo
c++ xcode linker-errors armadillo
edited Nov 17 '18 at 10:45
Suvo
asked Nov 16 '18 at 23:19
SuvoSuvo
227
227
Please add the actual error message from the linker. It should be right before the output you posted. Probably your code is also required to answer the question.
– user10605163
Nov 16 '18 at 23:38
-O2 isn't a linker flag, and g++ accepts and convayes linker flags to the linker, it acts like a driver in that case. Is XCode useing clang these days? If you are using g++ in XCode the -O2 -larmadillo should be a compiler flag not a linker flag. I also assume that because it works from the shell that the library is in g++'s search paths already so unless Xcode is rewriting the entire PATH environment variable then it should be able to find it.
– johnathan
Nov 17 '18 at 0:46
I have added the code in the original posting, and also the actual error.
– Suvo
Nov 17 '18 at 10:32
I have tried building without the -O2 flag. It still provides the same error in Xcode. But I can build the code using the command prompt.
– Suvo
Nov 17 '18 at 10:50
add a comment |
Please add the actual error message from the linker. It should be right before the output you posted. Probably your code is also required to answer the question.
– user10605163
Nov 16 '18 at 23:38
-O2 isn't a linker flag, and g++ accepts and convayes linker flags to the linker, it acts like a driver in that case. Is XCode useing clang these days? If you are using g++ in XCode the -O2 -larmadillo should be a compiler flag not a linker flag. I also assume that because it works from the shell that the library is in g++'s search paths already so unless Xcode is rewriting the entire PATH environment variable then it should be able to find it.
– johnathan
Nov 17 '18 at 0:46
I have added the code in the original posting, and also the actual error.
– Suvo
Nov 17 '18 at 10:32
I have tried building without the -O2 flag. It still provides the same error in Xcode. But I can build the code using the command prompt.
– Suvo
Nov 17 '18 at 10:50
Please add the actual error message from the linker. It should be right before the output you posted. Probably your code is also required to answer the question.
– user10605163
Nov 16 '18 at 23:38
Please add the actual error message from the linker. It should be right before the output you posted. Probably your code is also required to answer the question.
– user10605163
Nov 16 '18 at 23:38
-O2 isn't a linker flag, and g++ accepts and convayes linker flags to the linker, it acts like a driver in that case. Is XCode useing clang these days? If you are using g++ in XCode the -O2 -larmadillo should be a compiler flag not a linker flag. I also assume that because it works from the shell that the library is in g++'s search paths already so unless Xcode is rewriting the entire PATH environment variable then it should be able to find it.
– johnathan
Nov 17 '18 at 0:46
-O2 isn't a linker flag, and g++ accepts and convayes linker flags to the linker, it acts like a driver in that case. Is XCode useing clang these days? If you are using g++ in XCode the -O2 -larmadillo should be a compiler flag not a linker flag. I also assume that because it works from the shell that the library is in g++'s search paths already so unless Xcode is rewriting the entire PATH environment variable then it should be able to find it.
– johnathan
Nov 17 '18 at 0:46
I have added the code in the original posting, and also the actual error.
– Suvo
Nov 17 '18 at 10:32
I have added the code in the original posting, and also the actual error.
– Suvo
Nov 17 '18 at 10:32
I have tried building without the -O2 flag. It still provides the same error in Xcode. But I can build the code using the command prompt.
– Suvo
Nov 17 '18 at 10:50
I have tried building without the -O2 flag. It still provides the same error in Xcode. But I can build the code using the command prompt.
– Suvo
Nov 17 '18 at 10:50
add a comment |
1 Answer
1
active
oldest
votes
I was able to build successfully by installing macport.
Here are the steps:
Download and install macport from https://www.macports.org/.
Set Library path as /opt/local/lib.
Set Header path as /opt/local/include.
Set Other Linker Flags as -larmadillo.
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%2f53346621%2fgetting-xcode-c-linker-error-when-trying-to-run-an-example-using-armadillo-lib%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I was able to build successfully by installing macport.
Here are the steps:
Download and install macport from https://www.macports.org/.
Set Library path as /opt/local/lib.
Set Header path as /opt/local/include.
Set Other Linker Flags as -larmadillo.
add a comment |
I was able to build successfully by installing macport.
Here are the steps:
Download and install macport from https://www.macports.org/.
Set Library path as /opt/local/lib.
Set Header path as /opt/local/include.
Set Other Linker Flags as -larmadillo.
add a comment |
I was able to build successfully by installing macport.
Here are the steps:
Download and install macport from https://www.macports.org/.
Set Library path as /opt/local/lib.
Set Header path as /opt/local/include.
Set Other Linker Flags as -larmadillo.
I was able to build successfully by installing macport.
Here are the steps:
Download and install macport from https://www.macports.org/.
Set Library path as /opt/local/lib.
Set Header path as /opt/local/include.
Set Other Linker Flags as -larmadillo.
answered Nov 17 '18 at 11:34
SuvoSuvo
227
227
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%2f53346621%2fgetting-xcode-c-linker-error-when-trying-to-run-an-example-using-armadillo-lib%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
Please add the actual error message from the linker. It should be right before the output you posted. Probably your code is also required to answer the question.
– user10605163
Nov 16 '18 at 23:38
-O2 isn't a linker flag, and g++ accepts and convayes linker flags to the linker, it acts like a driver in that case. Is XCode useing clang these days? If you are using g++ in XCode the -O2 -larmadillo should be a compiler flag not a linker flag. I also assume that because it works from the shell that the library is in g++'s search paths already so unless Xcode is rewriting the entire PATH environment variable then it should be able to find it.
– johnathan
Nov 17 '18 at 0:46
I have added the code in the original posting, and also the actual error.
– Suvo
Nov 17 '18 at 10:32
I have tried building without the -O2 flag. It still provides the same error in Xcode. But I can build the code using the command prompt.
– Suvo
Nov 17 '18 at 10:50