|
PS - #include <someHeader.h> - the '<' and '>' included headers indicate that they are in the compiler's PATH (or something like that - files like 'stdio.h' and 'vector's (without the '.h' suffix) in .cpp). #include "someHeader.h" are for files included via the projects settings includes. I have never came across the ="" nomenclature - my first instinct is to tell you to ditch it and use the "" include method. But I'm not an expert on that - all I can say is what I've done has always worked.
|
|
|
|
|
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.
modified 23-Jan-23 5:21am.
|
|
|
|
|
#include <glfw glfw3.h="">
is what editor to lounge did. Not me
#include <glfw\glfw3.h> is what was supposed to be sent.
Something was awry.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Well you could have used the Edit button below the message to correct it.
|
|
|
|
|
I know. I just didn't see the first time.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
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
|
|
|
|
|
Done that, too.
This is another problem related to compilation and include files.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
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
|
|
|
|
|
BS. Not true.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
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... 
|
|
|
|
|
It's another problem related to include files and VS. Not static linking with static.
Sorry premature conclusion.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
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
|
|
|
|
|
guys. I am not ranting. I have done all the suggestions, checked all the boxes, VS will not recognize the include statement it's frustration.
It's not the static library issue anymore. I used the GLFW test program example from their website. Simple C program. VS will flag their include as not found even when the path is fulled included as additional include
GLFW folks are also working it.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
So you're the type that argues all day long - got it. You may wish to read your original post again. Clearly, you think that's not ranting. It is... but whatever.
Jeremy Falcon
|
|
|
|
|
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
|
|
|
|
|
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 am robot.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
whatever
"A little time, a little trouble, your better day"
Badfinger
modified 23-Jan-23 20:25pm.
|
|
|
|
|
Yes. not charade
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
|
Looking for a job?
Never mind you already work for MS.
"A little time, a little trouble, your better day"
Badfinger
modified 24-Jan-23 0:17am.
|
|
|
|
|
jmaida wrote: I will calmly say VS is not a user/programmer friendly application.
I started with hand written scripts.
Then I think I went to Borland IDE.
Then the first Microsoft IDE (not called VS)
Finally then I go to make files, then maven, then back to VS and then back to make/maven, then back to VS (going back and forth several times.) Eclipse is in there some where but I gave up on that right away (twice actually.)
And at least one custom built build system in there as well.
None of them were user friendly.
Might note of course that I have written many applications also and the universal truth is that power and simplicity are not possible in the same application.
The command line tools cat/type are pretty dang easy to use.
The editor that I have been using for 20 years (not part of an IDE) still manages to make me jump through hoops every time I have to install it on new box just to get it to work the way I want.
jmaida wrote: But I will solve this problem.
Having fought with VS many times, all I can say is that there is a way to solve the problem you described.
|
|
|
|
|
All that you have said, is very familiar to me, Eclipse, VS, Borland, Codeblocks, Geany (weird little editor/app) and of course Linux stuff with it's own IDE baggage (I have forgotten must of it and it's weird vi editor)
For windows environments, I settled on Codeblocks because it stayed relatively the same as far as the interfacing, program settings, etc. Their editor is quite good, one of the best, I think.
They add some new plugins now and then, but not too pushy.
But if someones puts it down, I let go as not their cup of tea.
We all have our fancies. I did business with a German company years ago and their programmers and I had no problems working together other some German/English language issues, but we all had similar likes and dislikes.
Thanks for encouragement. VS can be frustratingly fluid.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
