-
Notifications
You must be signed in to change notification settings - Fork 565
make fails miserably #317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
What compiler are you using? What version of it? It seems like you are not giving it appropriate |
Ah right, I forgot to mention that one. I just installed the latest MinGW, Version 6.3.0-1 and gcc version is 6.3.0. |
@LinaSchad commented on 15 Jun 2018, 15:11 CEST:
Try running the |
Did that, and it worked now. Still, make fails with errors that I posted first :/ Oh and I also tried it with the |
@LinaSchad commented on 15 Jun 2018, 15:11 CEST:
Can you point me to exact installer that you have used? There is a distinction between MinGW and MinGW64, AFAIK. |
I have no clue how to do a quote properly and sorry that I didn't tell you the important things right away, I haven't programmed for Windows quite a while. I used this one: MinGW and that's the exact output of |
Thank you for the information. I have tried and downloaded it. It is as I expected. MinGW is not built with C++11 threading support. If you look into /* Define if gthreads library is available. */
/* #undef _GLIBCXX_HAS_GTHREADS */
I suggest that you abandon MinGW in favour of some MinGW64 distribution. If you can do without MSYS I would go for Stephan T. Lavavej's distro. Or try MSYS2. In any case, I would suggest using CMake based build system for log4cplus on Windows instead of the Autotools based one. |
Oh wow, thank you so much! So if I'm going with MinGW64 I should be safe? |
@LinaSchad commented on 15 Jun 2018, 16:39 CEST:
Yes. |
I am closing this on assumption that MinGW64 solves your issue. |
Unfortunately it doesn't totally solve my problem :( After getting over one obstacle, that was installing the compiler in a folder without a space, I face now the problem, that make fails because of this error:
I'm feeling quite dump already, I never had such big problems with a framework yet :( I'm pretty sure I'm doing something wrong, but I just can't see what. |
Use the CMake based build instead. That should work. This is probably because of missing appropriate This should be documented. |
Add missing _WIN32_WINNT. This fixes GitHub issue log4cplus#317.
I have committed some changes to the Autotools build to fix your builds. I will be merging this to master and 2.0.x eventually, but if you want to, you can check out master from wilx/log4cplus. |
Okay, I somehow over read that part where the readme says one should use the CMake build. I was able to build the log4cplus part in Visual Studio. I just don't understand know why it's not found, when I try to include it in my project. I provided the path to the include folder in ´additional include directories´ and I also told my project to use ´log4cplus.lib´ as one of the ´additional dependencies´. I guess I now have just plain problems understanding how to include a library in C++ with Visual Studio :/ |
Oh and your version does come a lot further, but make is now crashing, because of |
This is just that you have to do |
Hi, with the option it's almost working now I think. The only problem is, that it looks for QtGlobal, since I don't use Qt, I would highly prefer not to get involved with that. Is it possible to omit the qtXdebugappender in general? |
@LinaSchad commented on 25 Jun 2018, 11:52 CEST:
The Qt appenders do not have to be built. Just configure with |
Cool, I got that one know. If you could possibly help me with one last thing, I tried to include it in my project and I told VS the folder path in 'additional include directories' and I also tried to tell the linker to look for a log4cplus.lib, neither worked. I still get the error "cannot open source file "log4cplus"". For the additional include directory I tried the highest level of log4cplus folders, the include folder and the log4cplus folder inside the include one. I know that this is a very basic and noob thing, but it's so long ago that I programmed with C++ and I can't get it right. Google also didn't help me much. |
@LinaSchad commented on 25 Jun 2018, 12:21 CEST:
If your intended use as part of Visual Studio based project then you can throw all of your effort up to this point away. Libraries compiled with MinGW/GCC are not compatible with Visual Studio compiler. You have to compile log4cplus with Visual Studio compiler if you want to use it in its projects. |
Oh damn it, well I did that just now and it worked. I still cannot link it for some reason. |
Nevermind I found my problem. I forgot to add the path in the additional library directories. Thanks a lot for helping me though. |
Hi there :)
I just wanted to start using log4cplus, because I really need a logging framework and it looks awesome. I need to use it on Windows 10 and I was able to run ./configure, but just with --disable-dependency-tracking because with just ./configure I got an error saying "Something went wrong bootstrapping makefile fragments for automatic dependency tracking. ..." When I now try to make I get this output:
I'd really appreciate help, thanks in advance :)
The text was updated successfully, but these errors were encountered: