:-1: error: symbol(s) not found for architecture x86_64
-
@jsulm Yes, but this would touch the unit test, i have been given conditions not to change the unit test.
@Dhara I don't know your requirements, but actually tests should be adapted to production code not other way around.
Alternative would be to return char* instead of a string, but I never would do this just because unit tests would like to have it this way. -
@Dhara I don't know your requirements, but actually tests should be adapted to production code not other way around.
Alternative would be to return char* instead of a string, but I never would do this just because unit tests would like to have it this way. -
@jsulm : another question if you could assist please, i get this error now :
duplicate symbol _main in: test_user.o test_group.o@Dhara said in :-1: error: symbol(s) not found for architecture x86_64:
_main
it means that what ever _main is, its include in both
test_user and test_groupThis often happens if its a variable and its define in .h file.
So what is _main ?
function / variable ? -
@Dhara said in :-1: error: symbol(s) not found for architecture x86_64:
_main
it means that what ever _main is, its include in both
test_user and test_groupThis often happens if its a variable and its define in .h file.
So what is _main ?
function / variable ? -
@mrjj there is no variable named _main or even a function named that. i do have one main.cpp file.
-
There's no such restriction in TDD.
In TDD, the goal is to have your code tested all along, not that the tests are written in stones and that you should workaround them in your production code.
If a function needs to have its signature changed, then update the test so you can validate the new version of that function.
-
There's no such restriction in TDD.
In TDD, the goal is to have your code tested all along, not that the tests are written in stones and that you should workaround them in your production code.
If a function needs to have its signature changed, then update the test so you can validate the new version of that function.
-
There's no such restriction in TDD.
In TDD, the goal is to have your code tested all along, not that the tests are written in stones and that you should workaround them in your production code.
If a function needs to have its signature changed, then update the test so you can validate the new version of that function.
I now get :
Undefined symbols for architecture x86_64: "contact::setName(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >)", referenced from: group::group(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >) in group.oAny suggestions?
-
Hi
I am quite new to QT. I have created a subdirs project that has the main app part and also test unit project in it. However when i build the whole project i get errors of the kinds below:
Undefined symbols for architecture x86_64: "user::setStatus(user::Status)", referenced from: TestUser::cannotSetNullUserStatus() in test_user.o TestUser::canChangeUserStatusToOffline() in test_user.o TestUser::canChangeUserStatusToOnline() in test_user.o TestUser::copyOfUserSharesStatus1() in test_user.o TestUser::copyOfUserSharedStatus2() in test_user.o "user::operator=(user const&)", referenced from: void std::__1::list<user, std::__1::allocator<user> >::assign<user const*>(user const*, user const*, std::__1::enable_if<__is_input_iterator<user const*>::value, void>::type*) in test_group.o void std::__1::list<user, std::__1::allocator<user> >::assign<std::__1::__list_const_iterator<user, void*> >(std::__1::__list_const_iterator<user, void*>, std::__1::__list_const_iterator<user, void*>, std::__1::enable_if<__is_input_iterator<std::__1::__list_const_iterator<user, void*> >::value, void>::type*) in test_group.o "bool QTest::qCompare<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, char [11]>(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, char const (&) [11], char const*, char const*, char const*, int)", referenced from: TestGroup::copyOfGroupSharesName1() in test_group.o TestGroup::contactFromGroupSharesName1() in test_group.o TestGroup::contactFromGroupSharesName2() in test_group.o``` Can anyone please guide me where i am wrong? I can share in the cpp code file too:user::Status& user::setStatus(user::Status status) {
if (!isNull()) {
userStatus = new user::Status;
*userStatus = status;
}
return *userStatus;
}The header file has this method declaration too. I need to somehow finish this soon, and i tried googling but i dont understand what i should do. Please help.Thanks alot for the help that you have been giving me. I managed to fix all the issues and also the duplicate error meant that i had to create two subprojects for both the test cases, i have no clue what was repeating but doing this solved the issue.
I updated the test cases too so that they would match QCOMPARE's definition.
I also deleted std -= libc++ and the other line and also removed C++11 config line too. Removing these lines did not harm the project.
-
Hi,
@Dhara
please move it solved state if u have the got solution and post ur solution so others will be helped from ur answer.Thanks,
-
@SGaist said in :-1: error: symbol(s) not found for architecture x86_64:
CONFIG += c++11
I removed the same and built the whole project after a clean but i still face the same issue. Is it necessary that my cpp files should extend QObject ?
@Dhara same issue exist for me too
