While building a dll in DevC++, I get the message "The input line is too long. make.exe: *** [FoundationKitDLL.dll] Error 255 Execution terminated" (Log showing the object files posted at bottom).
Can anyone point me in the right direction on how to get a dll to link/build using DevC++ and MinGW?
Although I can get this particular dll to build by moving my project and obj files to the same directory as the source, in general this is not acceptable as the build is part of a multi-platform and mult-compiler project. Further, for another dll for this project there will be approximately 200 object files, in which case even if I put the project and obj files in the same directory, the command line will be too long.
i've had similar problems. I made my directory names much smaller, and similarly you could do the same with file names. It is only the final dll which would have to be either the file name, or renamed after the build.
Another option is to have the various c files #include 'd in a single master file, then you only build the one file. this would cater for your 200+ source file project. and maintain all file names and cross compiler/platform compatibility.
Tim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"Can anyone point me in the right direction on how to get a dll to link/build using DevC++ and MinGW? "
I should ask that differently. Can anyone point me in the right direction on how to get a dll to link/build for a project that has so many object files, it exceeds the normal 'input line' limit?
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
DevC++ 4.9.9.2
MinGW/gcc 3.3.1
Win2K
While building a dll in DevC++, I get the message "The input line is too long. make.exe: *** [FoundationKitDLL.dll] Error 255 Execution terminated" (Log showing the object files posted at bottom).
Can anyone point me in the right direction on how to get a dll to link/build using DevC++ and MinGW?
Although I can get this particular dll to build by moving my project and obj files to the same directory as the source, in general this is not acceptable as the build is part of a multi-platform and mult-compiler project. Further, for another dll for this project there will be approximately 200 object files, in which case even if I put the project and obj files in the same directory, the command line will be too long.
I assume there has to be a way to do this.
Thanks,
Doug
dllwrap.exe --output-def libFoundationKitDLL.def --driver-name c++ --implib libFoundationKitDLL.a ../../../src/vcf/FoundationKit/FoundationKit.o ../../../src/vcf/FoundationKit/Win32Condition.o ../../../src/vcf/FoundationKit/Win32FilePeer.o ../../../src/vcf/FoundationKit/Win32FileStream.o ../../../src/vcf/FoundationKit/Win32LibraryPeer.o ../../../src/vcf/FoundationKit/Win32LocalePeer.o ../../../src/vcf/FoundationKit/Win32Mutex.o ../../../src/vcf/FoundationKit/Win32Peer.o ../../../src/vcf/FoundationKit/Win32ProcessIORedirector.o ../../../src/vcf/FoundationKit/Win32ProcessPeer.o ../../../src/vcf/FoundationKit/Win32Registry.o ../../../src/vcf/FoundationKit/Win32ResourceBundle.o ../../../src/vcf/FoundationKit/Win32SemaphorePeer.o ../../../src/vcf/FoundationKit/Win32SystemPeer.o ../../../src/vcf/FoundationKit/Win32SystemToolkit.o ../../../src/vcf/FoundationKit/Win32Thread.o ../../../src/vcf/FoundationKit/BasicException.o ../../../src/vcf/FoundationKit/Event.o ../../../src/vcf/FoundationKit/EventHandler.o ../../../src/vcf/FoundationKit/PropertyChangeEvent.o ../../../src/vcf/FoundationKit/ThreadEvent.o ../../../src/vcf/FoundationKit/BasicInputStream.o ../../../src/vcf/FoundationKit/BasicOutputStream.o ../../../src/vcf/FoundationKit/Directory.o ../../../src/vcf/FoundationKit/File.o ../../../src/vcf/FoundationKit/FilePath.o ../../../src/vcf/FoundationKit/FileStream.o ../../../src/vcf/FoundationKit/MemoryStream.o ../../../src/vcf/FoundationKit/Stream.o ../../../src/vcf/FoundationKit/TextInputStream.o ../../../src/vcf/FoundationKit/TextOutputStream.o ../../../src/vcf/FoundationKit/CommandLine.o ../../../src/vcf/FoundationKit/Condition.o ../../../src/vcf/FoundationKit/DateTime.o ../../../src/vcf/FoundationKit/Dictionary.o ../../../src/vcf/FoundationKit/ErrorLog.o ../../../src/vcf/FoundationKit/Library.o ../../../src/vcf/FoundationKit/MessageLoader.o ../../../src/vcf/FoundationKit/MIMEType.o ../../../src/vcf/FoundationKit/Mutex.o ../../../src/vcf/FoundationKit/PackageInfo.o ../../../src/vcf/FoundationKit/Parser.o ../../../src/vcf/FoundationKit/ProcessWithRedirectedIO.o ../../../src/vcf/FoundationKit/Registry.o ../../../src/vcf/FoundationKit/Semaphore.o ../../../src/vcf/FoundationKit/StringsMessageLoader.o ../../../src/vcf/FoundationKit/StringUtils.o ../../../src/vcf/FoundationKit/System.o ../../../src/vcf/FoundationKit/SystemToolkit.o ../../../src/vcf/FoundationKit/TextCodec.o ../../../src/vcf/FoundationKit/Thread.o ../../../src/vcf/FoundationKit/VCFMath.o ../../../src/vcf/FoundationKit/VCFProcess.o ../../../src/vcf/FoundationKit/VCFString.o ../../../src/vcf/FoundationKit/XMLParser.o ../../../src/vcf/FoundationKit/Locales.o ../../../src/vcf/FoundationKit/Object.o ../../../src/vcf/FoundationKit/ObjectWithEvents.o ../../../src/vcf/FoundationKit/Resource.o ../../../src/vcf/FoundationKit/ResourceBundle.o ../../../src/vcf/FoundationKit/Class.o ../../../src/vcf/FoundationKit/ClassRegistry.o ../../../src/vcf/FoundationKit/InterfaceClass.o ../../../src/vcf/FoundationKit/VariantData.o -L"C:/Dev-Cpp/lib" -lrpcrt4 -lkernel32 -luser32 -lgdi32 -lwinspool -lcomdlg32 -ladvapi32 -lshell32 -lole32 -loleaut32 -luuid -lodbc32 -lodbccp32 -lversion -s -o FoundationKitDLL.dll The input line is too long. make.exe: *** [FoundationKitDLL.dll] Error 255 Execution terminated
i've had similar problems. I made my directory names much smaller, and similarly you could do the same with file names. It is only the final dll which would have to be either the file name, or renamed after the build.
Another option is to have the various c files #include 'd in a single master file, then you only build the one file. this would cater for your 200+ source file project. and maintain all file names and cross compiler/platform compatibility.
Tim
"Can anyone point me in the right direction on how to get a dll to link/build using DevC++ and MinGW? "
I should ask that differently. Can anyone point me in the right direction on how to get a dll to link/build for a project that has so many object files, it exceeds the normal 'input line' limit?
Thanks