VS 2022 is not C friendly
-
I have been trying to create a static library (in C) that uses another published static library. No where does VS do I have link options to include that library. VS SUCKS
"A little time, a little trouble, your better day" Badfinger
You can try to link the static lib by specifying this pragma statement in any c source file.
#pragma comment(lib, "c:\\your_folder\\your_lib.lib")
-
I have been trying to create a static library (in C) that uses another published static library. No where does VS do I have link options to include that library. VS SUCKS
"A little time, a little trouble, your better day" Badfinger
The reason the VC++ static library project does not have the linkage option is that the static library does not have to link to any library, the source code file only needs to include the headers file to compile correctly. The executable project that uses your C static library must link with both static libs in the link options.
-
The reason the VC++ static library project does not have the linkage option is that the static library does not have to link to any library, the source code file only needs to include the headers file to compile correctly. The executable project that uses your C static library must link with both static libs in the link options.
-
The reason the VC++ static library project does not have the linkage option is that the static library does not have to link to any library, the source code file only needs to include the headers file to compile correctly. The executable project that uses your C static library must link with both static libs in the link options.
-
Understood. Thank you. Still not VS fan, but I have no choice.
"A little time, a little trouble, your better day" Badfinger
You're welcome. I happened to know the answer because I encountered the same problem some time ago.
-
I have been trying to create a static library (in C) that uses another published static library. No where does VS do I have link options to include that library. VS SUCKS
"A little time, a little trouble, your better day" Badfinger
-
Thanks. Pragma's seem to the answer to all the weird VS behavior I have encountered such as fopen vs fopen_s etc.
"A little time, a little trouble, your better day" Badfinger
-
jmaida wrote:
weird VS behavior I have encountered such as fopen vs fopen_s etc.
Again, that has nothing to do with Visual Studio, but only the code that you are writing.
A lot of members here at Code Project love to hate on Visual Studio for no intelligent reason at all. "I got into a car crash this morning, I hate Visual Studio." "I stubbed my toe getting out of bed this morning, Visual Studio sucks!!" "I don't know what I am doing, it's Visual Studio's fault!" the list literally goes on forever... :sigh:
-
This has nothing to do with Visual Studio, but only the parameters you have set in your project. Including libraries, whether static or dynamic, is a standard part of VS project files.
All of which may be true, but... A developer may complain that accomplishing such-n-such is difficult/tricky/whatever -- and C falls into that category. Then Microsoft comes along and says that Visual Studio will make it easy (and it definitely makes many things easy). But if VS doesn't make that one thing easy, then it SUCKS!, I mean it won't satisfy that developer's immediate need. I don't use Visual Studio much because it generally doesn't do anything I need done, not because I don't like it. What little C I still do, I don't do with Visual Studio. I really like C#, which in part may have been designed specifically for Visual Studio, so VS is very good for C# (and .net). I miss Turbo C.
-
All of which may be true, but... A developer may complain that accomplishing such-n-such is difficult/tricky/whatever -- and C falls into that category. Then Microsoft comes along and says that Visual Studio will make it easy (and it definitely makes many things easy). But if VS doesn't make that one thing easy, then it SUCKS!, I mean it won't satisfy that developer's immediate need. I don't use Visual Studio much because it generally doesn't do anything I need done, not because I don't like it. What little C I still do, I don't do with Visual Studio. I really like C#, which in part may have been designed specifically for Visual Studio, so VS is very good for C# (and .net). I miss Turbo C.
PIEBALDconsult wrote:
A developer may complain that accomplishing such-n-such is difficult/tricky/whatever
That is an essential part of the job, and why documentation and help systems are created. I come from an age before Google, so I had to learn the hard way - mainly by buying, and studying, the books.
-
PIEBALDconsult wrote:
A developer may complain that accomplishing such-n-such is difficult/tricky/whatever
That is an essential part of the job, and why documentation and help systems are created. I come from an age before Google, so I had to learn the hard way - mainly by buying, and studying, the books.
'Xactly. Me too. Kids these days expect everything to be handed to them. I also learned on OpenVMS, which has a debugger, but it's practically unusable.
-
Understood. Thank you. Still not VS fan, but I have no choice.
"A little time, a little trouble, your better day" Badfinger
Don't know if you will find it helpful, but here's an article on configuring Visual Studio for a C++ project. It deals with the same issue you face, and might give you more insights into Visual Studio's processes - maybe. [DWinLib Build Process](https://www.codeproject.com/Articles/5292382/DWinLib-Build-Process). It can be a pain to set up, but gives a lot of power when you've figured it out.
Our Forgotten Astronomy | Object Oriented Programming with C++ | Wordle solver
-
A lot of members here at Code Project love to hate on Visual Studio for no intelligent reason at all. "I got into a car crash this morning, I hate Visual Studio." "I stubbed my toe getting out of bed this morning, Visual Studio sucks!!" "I don't know what I am doing, it's Visual Studio's fault!" the list literally goes on forever... :sigh:
-
jmaida wrote:
weird VS behavior I have encountered such as fopen vs fopen_s etc.
Again, that has nothing to do with Visual Studio, but only the code that you are writing.
I TOTALLY disagree. The code I am working with is just a simple basic C libary. In VS I chose static library, etc. The problem is VS is way too complicated, trying to do to many things for too many types of language applications. I have used VS off and on for years so I know what I am talking about. I came back to it because of potential conversion of a large graphics application that will be "potentially" ported to it. I am quickly changing my mind as to whether it is worth it or not. The application is mostly window's agnostic.
"A little time, a little trouble, your better day" Badfinger
-
jmaida wrote:
weird VS behavior I have encountered such as fopen vs fopen_s etc.
Again, that has nothing to do with Visual Studio, but only the code that you are writing.
-
This has nothing to do with Visual Studio, but only the parameters you have set in your project. Including libraries, whether static or dynamic, is a standard part of VS project files.
-
Don't know if you will find it helpful, but here's an article on configuring Visual Studio for a C++ project. It deals with the same issue you face, and might give you more insights into Visual Studio's processes - maybe. [DWinLib Build Process](https://www.codeproject.com/Articles/5292382/DWinLib-Build-Process). It can be a pain to set up, but gives a lot of power when you've figured it out.
Our Forgotten Astronomy | Object Oriented Programming with C++ | Wordle solver
-
The reason the VC++ static library project does not have the linkage option is that the static library does not have to link to any library, the source code file only needs to include the headers file to compile correctly. The executable project that uses your C static library must link with both static libs in the link options.
I understand. The static library I am trying to create explicitly uses calls to another static library (which I did not create). I understand that both with be involved when used by a third application. I have been using CodeBlocks as my IDE of choice. Much more straight forward and has a great editor. Uses GCC compiler.
"A little time, a little trouble, your better day" Badfinger
-
All of which may be true, but... A developer may complain that accomplishing such-n-such is difficult/tricky/whatever -- and C falls into that category. Then Microsoft comes along and says that Visual Studio will make it easy (and it definitely makes many things easy). But if VS doesn't make that one thing easy, then it SUCKS!, I mean it won't satisfy that developer's immediate need. I don't use Visual Studio much because it generally doesn't do anything I need done, not because I don't like it. What little C I still do, I don't do with Visual Studio. I really like C#, which in part may have been designed specifically for Visual Studio, so VS is very good for C# (and .net). I miss Turbo C.