Stange -I effect with make and bad -L
I am trying to create an automated build system. It took me a little while to change the working wii generic file to a working make32 win32 file (using mingw32).
my make is here http://pastie.org/319482
The weird effect is that if I delete the previous path in ABS_INCL (line 31), the assembly doesn't work and complains about the missing header that is specified by the first path. Why is he doing this? I cannot track the problem.
The next problem is that when I fell into code that requires libcurl, I can still compile, but no longer link as expected. I added curl for my libs (line 47) and path (line 53) and it looks like I am including it correctly and the lib is in the correct order (I tried to touch as little as possible when converting wii to win32) and I see no problem ... Does anyone know why this is happening?
here is a simple source for testing with
#include <stdio.h>
void main2();
int main( int argc, const char* argv[])
{
int a=0;
printf("hey");
main2();
return 0;
}
#include <curl/curl.h>
void main2()
{
CURL *curl = curl_easy_init();
curl_easy_cleanup(curl);
}
You won't get many answers here - I'm going to go out on a limb and tell you this because of your very poorly written title. I read it maybe 20 times as it scrolled down the homepage and I still don't get it. There is an obvious spelling error and I want to go in and fix it, but then there are all the oddities with "-l" and "-L" and I can't tell where you're going with that.
So most people will look at it and just blank and move on. Assuming they got past that, you were unable to add useful information contained in your makefile to this question, and so you must go away and read it on another site.
Finally, as another hurdle, your makefile is too long to read and consume easily. So, assuming that someone like me, who is indeed defined, goes and reads it, it's too hard to tell where the problem might be. You need to edit it to maybe ten lines or less and then, assuming you weren't able to figure out the problem, you could only post a few lines that showed the problem in your question, and then with a decent title and some good descriptive text, you will probably get an answer.
I guess the answer to your question is not that difficult, you managed to trick it to the point that most people didn't even bother.
source to share