-
Notifications
You must be signed in to change notification settings - Fork 116
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
Develop branch is broken #154
Comments
What system and compiler are you working on. I just verified that I am able to rebuild and successfully execute the test suite on a PC. This Tiffio class has been successfully used for a while and has not changed recently. |
I'm on LInux. Trying to build with GCC 5.4.0 got error posted in the first message. |
Does your pull request #155 resolve this, or is this still a problem. |
#155 is a completely dufferent thing, it is about missed tools in the CMakeLists.txt |
OK. I do not know how to change the code to fix this, and it works for my current PC visual studio setup. |
Hi @alexbruy, did you ever get a solution to this problem? I'm running into the same thing trying to build the In fact, even to get this far, I've also had to work around #166 by removing all references to Any suggestions? Terry |
I've just today pushed new code and build information for both make and cmake to the develop branch.. I was able to compile all code on linux. I will close this issue, but feel free to reopen, or open another one if there are still problems. |
@dtarb , what version of Linux are you using? Are you using any special compiler switches? I'm using Ubuntu 14.04 LTS and with default installation of C and C++. I cloned a new copy of the Develop branch, did the cmake, and make as follows, and I'm getting these errors (I think same as @alexbruy describes above in the OP). It seems to be having trouble compiling tiffIO.cpp
Terry |
I am using ubuntu 16.04.4 LTS The difference I would be most suspicious of is the compiler. I am using C compiler GNU 7.3.0. Your message above indicates GNU 4.8.4. I get similar messages to the ones you are getting, but they do not get reported as errors, rather they are given as warnings. For example the first one I get is
It may take a C++ template classes guru to help us out with this. Look at https://github.com/dtarb/TauDEM/blob/Develop/GCC.sh where I give the steps I used to upgrade the C++ compiler. I do not know if compiler version is the root cause of the warning/error problem or whether there is an error permissiveness setting somewhere that would help you. But I do think you may need the newer compiler for some other functionality that has been added. |
@twilkinson Try pull a copy of the HeaderRefactor branch. I thought I should try and address the problem that was giving me a warning and you an error and which when I investigated seemed to be due to a forward declaration error. I have tried to fix this in the new branch, and on my computer no longer get the compiler warning above. The strategy I took, in case you are curious is described in https://github.com/dtarb/TauDEM/blob/HeaderRefactor/UpdateNotes.txt. I'll merge this branch into Develop once it has been tested a bit more, but my tests seem to check out so far. |
@dtarb, thanks for this. The HeaderRefactor branch now works fine for me on both Ubuntu 14.04/C++v4.8.4 and Centos 7.4/C++v5.4.0. I did have to add the following (from https://stackoverflow.com/questions/10851247/how-to-activate-c-11-in-cmake) near the top of CMakeLists.txt to activate the C++ 11 standard:
Fyi, using this branch I was also able to remove the AND the additional information in the github README.txt is very useful! Thanks. |
Glad it is working. Looking at that stack overflow answer it seems like the macro you added may be limited to GCC (for CMake versions <3.1). It would be simpler to just add I think that removing the -netlyr option should have been possible on the Develop branch since commit 951ed55 on Nov 18 https://github.com/dtarb/TauDEM/commits/Develop/src/streamnet.cpp, but perhaps you have not been able to compile since then. |
Yes, it does look like the macro I got from stackoverflow will only work for GCC - luckily that's what I have :-). No problem upgrading And you are right about the Looks all good now. |
Thanks. I updated CMakeLists and merged this branch into develop. |
I tried to improve build system a bit in
Develop
branch, but looks like it is brokenThe text was updated successfully, but these errors were encountered: