The library seems to be 'gdi32':
https://msdn.microsoft.com/en-us/library/vs/alm/dd144925%28v=vs.85%29.aspx
A library can be either static or dynamic. Static library is just a collection of object code and linker effectively copies code into executable during linking. Statically linked executable is a large monolith, but self-sufficient.
Dynamic library is object code too, but rather than copying actual code, the linker adds call code 'stubs' into the executable. When the executable (your program) is run, the library file is linked in and code is executed from it. Thus, the executable file does not work without the library file(s). The executable file is smaller and many programs may use same library; less duplication.
In *nix a dynamic library has extension .so
In OS X a dynamic library has extension .dyld
In Windows a dynamic library has extension .dll, but there is also a .lib file created with the dll that is a small static library containing the stubs thatthe linker inserts into the executable for the executable to link the dll.
The linker of GCC in Windows uses some mixture of library types.
https://msdn.microsoft.com/en-us/library/vs/alm/dd144925%28v=vs.85%29.aspx
A library can be either static or dynamic. Static library is just a collection of object code and linker effectively copies code into executable during linking. Statically linked executable is a large monolith, but self-sufficient.
Dynamic library is object code too, but rather than copying actual code, the linker adds call code 'stubs' into the executable. When the executable (your program) is run, the library file is linked in and code is executed from it. Thus, the executable file does not work without the library file(s). The executable file is smaller and many programs may use same library; less duplication.
In *nix a dynamic library has extension .so
In OS X a dynamic library has extension .dyld
In Windows a dynamic library has extension .dll, but there is also a .lib file created with the dll that is a small static library containing the stubs thatthe linker inserts into the executable for the executable to link the dll.
The linker of GCC in Windows uses some mixture of library types.
Hi,
Can anyone tel me why am getting permission denied,ld returned 1 exit status in dev c??? Actually when i compiled that program first time it was compiled and run also. But repeatedly i changed sme things and wen i was compilin again and again i got this problem. Sep 05, 2014 Error Id returned 1 exit status Error Id returned 1 exit status. Hi, I'm just beginning computer programming for a class in school. I adapted the program. When I attempted to compile it with the Dev C compiler, it gave the message 'Error Id returned 1 exit status'.
![Dev Dev](https://gss0.baidu.com/-4o3dSag_xI4khGko9WTAnF6hhy/zhidao/wh%3D600%2C800/sign=750c3bc6dd43ad4ba67b4ec6b2327697/d058ccbf6c81800ab5e74f6dbd3533fa828b4757.jpg)
I'm still a beginner for C programming. In my assignment I've encountered this problem and I know is a linker problem but I'm not sure how to solve it. I'm trying to link 3 files which 2 .c files and 1 .h file. Below are the codes for my file:
These 3 files are my codings. I hope someone can help me out. I'm stuck at his problem for long time. Thanks in advance. Appreciate your help.
Dev C++ Id Returned 1 Exit Status
- 5 Contributors
- forum 4 Replies
- 11,374 Views
- 5 Years Discussion Span
- commentLatest Postby Sean1234$Latest Post
Banfa597
I think you mean Ld returned 1 exit status.
Do you really mean you tried to link the 2 c files and the h file or do you mean you compiled the c files and tried to link the resulting objects?
The processor of building a program is
- Compile each individual source (.c) file producing an object file (.o or .obj)
- Link all the object files produced in stage 1 with any require libraries
NOTE 1: you neither compile or link header (.h) files, they are included into source (.c) files and the code the contain is compiled in that manner.
NOTE 2: It is very poor practice to #include source files (.c) into other source files (.c) as you have done in your driver.c listing. However if you must/do do that then you should not separately compile the source (.c) that you included.
Normally the IDE handles the build process for you so it would help us to know what tools, compiler tool-chain and/or IDE you are using.