VS 2022 is not C friendly
-
Ever seen a simple IDE?
-
Find the main header that controls everything. Make a single VS project with just that. Comment out all of the included headers. Even comment out the code. Get that to compile. Then uncomment one header and get that to compile. Etc. etc. If it is a big project it will take quite a while. I have gone through a process like that before. It wasn't fun, but I found the stupid effing mistake. It was my own mistake.
Our Forgotten Astronomy | Object Oriented Programming with C++ | Wordle solver
-
Code Blocks is more straight forward
"A little time, a little trouble, your better day" Badfinger
CB is specialized for C/C++ and Fortran, so it will be far simpler than VS, but again, it is not simple. BTW it was my first IDE, so I have some newbie dev experience with it, it was not hell, but it still required serious effort to configure.
-
I do not like to argue all day long. I am looking for helpful input. I have received it and I have taking everyone's advice, but I still cannot get VS to behave. Frustrating. OK. You can call it ranting. So what. I am an extremely experienced C programmer (I have also written code in C, Fortran, Cobol, Algol, PL/I ...) as well. Writing C code since K&R first publication, so feel qualified to complain. I am retired now and doing some experimenting using GLFW's VS libraries to facilitate porting a large body of work to VS for programmers at a former employer. I will calmly say VS is not a user/programmer friendly application. I have used it on and off since it first came out and it keeps getting worse. But I will solve this problem.
"A little time, a little trouble, your better day" Badfinger
Ok... whatever.
Jeremy Falcon
-
Ok... whatever.
Jeremy Falcon
-
I guess you are the whatever type. :)
"A little time, a little trouble, your better day" Badfinger
I guess you lack the self-awareness to see you proved my point about you looking to rant and argue. Since I know you're going to reply and continue this charade, you can have the last post. Still won't have the solution though.
Jeremy Falcon
-
I guess you lack the self-awareness to see you proved my point about you looking to rant and argue. Since I know you're going to reply and continue this charade, you can have the last post. Still won't have the solution though.
Jeremy Falcon
-
I guess you lack the self-awareness to see you proved my point about you looking to rant and argue. Since I know you're going to reply and continue this charade, you can have the last post. Still won't have the solution though.
Jeremy Falcon
-
I guess you lack the self-awareness to see you proved my point about you looking to rant and argue. Since I know you're going to reply and continue this charade, you can have the last post. Still won't have the solution though.
Jeremy Falcon
-
I guess you lack the self-awareness to see you proved my point about you looking to rant and argue. Since I know you're going to reply and continue this charade, you can have the last post. Still won't have the solution though.
Jeremy Falcon
-
I guess you lack the self-awareness to see you proved my point about you looking to rant and argue. Since I know you're going to reply and continue this charade, you can have the last post. Still won't have the solution though.
Jeremy Falcon
-
jmaida wrote:
#include <glfw glfw3.h=""> fails not matter how I reference that the directory it is located in. D:\code\glfw3.3.8\include NOT A TYPO ANYWHERE
Apart from the fact that the include statement is totally incorrect. And again, that is nothing to do with Visual Studio, but one for the compiler. Well, strictly speaking, it's the preprocessor, but we'll let that pass.
-
You can link to static lib from a static lib in VS in C. I've done it, but I'm not gonna tell you how. Why? Because of your attitude. Life's too short. Keep on Googling.
Jeremy Falcon
-
David O'Neil wrote:
If you selected 'static library project' it is set to CREATE a static library
Home dude isn't here to learn. He's here to rant.
Jeremy Falcon
-
A static library cannot use another static library. What exactly do you mean? Honestly VS is perfectly fine, it's, as almost always, the users... :laugh:
-
Try again, you can still write a static lib in C in VS2022. You don't need to use pragmas either. While I'm not a fan of VS these days as it's too bloated, at least be fair and do the research before saying something sucks because it can't do something - when it can. We're supposed to be mature professionals. Supposed to be...
Jeremy Falcon
-
Python?!? Hell no! But there are much better tools out there than VS, specially if one is interested in programming just in C, without any of those C++isms...
-
Code Blocks is more straight forward
"A little time, a little trouble, your better day" Badfinger
If you want to do JUST C, try taking a look at Pelle's C. None of the C++ stuff, just by default, compliant with the latest C standard. Freeware, but not Open Source. But certainly the price tag fits...
-
Well, if you're used to Turbo C, try Embarcadero C++Builder, though I personally don't like the price tags anymore... That's why I switched for my daily programming work to FreePascal+Lazarus instead of Delphi more than a decade ago.
-
doing so as we espeak. BTW reading your article too.
"A little time, a little trouble, your better day" Badfinger
Here is a suggestion. Stop ranting about something you are having problems with. Go to https://www.codeproject.com/Questions/ask.aspx[^] and post the full details, so people can try to help you. And make sure you check what you post, so you can fix any typos, and ensure that all code snippets are surrounded by the appropriate <pre> tags so it is readable, like:
#include "somefile.h"
int main()
{
printf("Hello, World!");return 0;}
Tags used in the above case are: <pre lang="C++"> and </pre>