Thread: Re: [Dev-C++] Newbie question on issue / bug reporting
Open Source C & C++ IDE for Windows
Brought to you by:
claplace
Menu
▾
▴
dev-cpp-users
|
From: sudhir k. <sud...@ya...> - 2005-08-11 07:17:03
|
--- Steve HiHighamststevejsjlto.ukukwrote: > Hi, > > I'm a newbie Dev-CpCppser although I have been > coding in C++ for several > years. > > I'm very pleased with Dev-CpCppHowever I've found a > couple of minor > features / bugs (see below). How do I report these? > > Kind Regards, > > Steve > > Issue 1 - Library Locations > ================== > When including libraries it is necessary to provide > a full path. Even > when the libraries are in the default location. For > example system > libraries in C:\Dev-CpCppib. Furthermore when > browsing for the directory > using the "Add Library of Object" button the library > is added using a > relative path. This has the following unfortunate > consequences:- > The project will fail to build if the location of > the project file > changes with respect to the install directories > (e.g. moving a complete > project will break the build). > The file name passed to the linker becomes much > larger (e.g. > ../../../../../../Dev-CpCppib/lilibuuid). This might > cause problems on > large projects. > > Issue 2 - Dual Monitor and / or large monitor issue > ================================== > I have installed Dev-CpCppn an AcAceraptop with dual > monitor support. > The second (plugged in) monitor is running at a > resolution of 1280 X > 1024. When I try to maximise Dev-CpCppn the second > monitor it only uses > the top 75% of the monitor. I have not experienced > this issue with any > other programs. > -- > > Steve HiHigham> > É +44 (0)1663 719830 > È +44 (0)7773 381215 > ststevejsjlto.ukukmamailtotstevejsjlto.ukuk > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software > Conference & EXPO September > 19-22, 2005 * San Francisco, CA * Development > LiLifecyclerPractices> Agile & Plan-Driven Development * Managing Projects > & Teams * Testing & QAQA> Security * Process Improvement & Measurement * > hthttp/wwwwwqsqeom/bsbscef > _______________________________________________ > Dev-cpcppsers mailing list > Dev-cpcppsers@lists.sosourceforgeet > TO UNUNSUBSCRIBE > hthttp/wwwww.brbrinksterom/nonoicysedevcppbubthtm> hthttps/lists.sosourceforgeet/lists/lilistinfoedevpcppsers > hi, In regard to your first issue: ================================= If your library doesn't resides in default library path, you can alternativily add the directory where your library files resides by adding "-L<dir_name>" to "additional commandline parameters" for c/c++ compiler or adding the the directory in the "directory" tab in "project options" .Now link the required library by adding "-l" option in the "parameters" tab .If you want to link "libXYZ.a" then the linker parameter will be "-lXYZ" e.g , you want to link with "c:\lib\libXYZ.a" then 1.)add "-Lc:\lib" to compilier paremeters or add the "c:\lib" directory in library directories. 2.)add "-lXYZ" in the linker options. Pardon for my english. Sudhir kumar porwal --------------------------------- Check out Yahoo! India Rakhi Special for Rakhi shopping, contests and lots more. http://in.promos.yahoo.com/rakhi/index.html |
|
From: Steve H. <st...@sj...> - 2005-08-11 15:33:38
|
sudhir kumar wrote: >--- Steve HiHighamststevejsjlto.ukukwrote: > > > >>Hi, >> >>I'm a newbie Dev-CpCppser although I have been >>coding in C++ for several >>years. >> >>I'm very pleased with Dev-CpCppHowever I've found a >>couple of minor >>features / bugs (see below). How do I report these? >> >>Kind Regards, >> >>Steve >> >>Issue 1 - Library Locations >>================== >>When including libraries it is necessary to provide >>a full path. Even >>when the libraries are in the default location. For >>example system >>libraries in C:\Dev-CpCppib. Furthermore when >>browsing for the directory >>using the "Add Library of Object" button the library >>is added using a >>relative path. This has the following unfortunate >>consequences:- >>The project will fail to build if the location of >>the project file >>changes with respect to the install directories >>(e.g. moving a complete >>project will break the build). >>The file name passed to the linker becomes much >>larger (e.g. >>../../../../../../Dev-CpCppib/lilibuuid). This might >>cause problems on >>large projects. >> >>Issue 2 - Dual Monitor and / or large monitor issue >>================================== >>I have installed Dev-CpCppn an AcAceraptop with dual >>monitor support. >>The second (plugged in) monitor is running at a >>resolution of 1280 X >>1024. When I try to maximise Dev-CpCppn the second >>monitor it only uses >>the top 75% of the monitor. I have not experienced >>this issue with any >>other programs. >>-- >> >>Steve HiHigham> >>É +44 (0)1663 719830 >>È +44 (0)7773 381215 >>› ststevejsjlto.ukukmamailtotstevejsjlto.ukuk >> >> >> >> >> >> >------------------------------------------------------- > > >>SF.Net email is Sponsored by the Better Software >>Conference & EXPO September >>19-22, 2005 * San Francisco, CA * Development >>LiLifecyclerPractices> Agile & Plan-Driven >> >> >Development * Managing Projects > > >>& Teams * Testing & QAQA> Security * Process >> >> >Improvement & Measurement * > > >>hthttp/wwwwwqsqeom/bsbscef >>_______________________________________________ >>Dev-cpcppsers mailing list >>Dev-cpcppsers@lists.sosourceforgeet >>TO UNUNSUBSCRIBE >>hthttp/wwwww.brbrinksterom/nonoicysedevcppbubthtm> >> >> >hthttps/lists.sosourceforgeet/lists/lilistinfoedevpcppsers > > > >hi, > > In regard to your first issue: >================================= > > If your library doesn't resides in default library >path, you can alternativily add the directory where >your library files resides by adding "-L<dir_name>" >to "additional commandline parameters" for c/c++ >compiler or adding the the directory in the >"directory" tab in "project options" .Now link the >required library by adding "-l" option in the >"parameters" tab .If you want to link "libXYZ.a" then >the linker parameter will be "-lXYZ" > > >e.g , you want to link with "c:\lib\libXYZ.a" then >1.)add "-Lc:\lib" to compilier paremeters or add the >"c:\lib" directory in library directories. > >2.)add "-lXYZ" in the linker options. > > > Pardon for my english. > > Sudhir kumar porwal > > > > > > >____________________________________________________ >Send a rakhi to your brother, buy gifts and win attractive prizes. Log on to http://in.promos.yahoo.com/rakhi/index.html > > > Sudhir, Thanks for your help. However this does not address the issue. The first approach to adding a library via the IDE is to use the "Add Library or Object" dialog. Using a standard library produces the following entries in the .dev file:- [Project] Libs= Linker=../../../../../Dev-Cpp/lib/libole32.a_@@_../../../../../Dev-Cpp/lib/liboleaut32.a_@@_ This compiles fine. However the entries use a relative path from the project directory to the library directory. In other words moving the project directory will break the build. This is not good. By editing the entries in the "Linker" box of the IDE we can ad the full path in. This improves the situation. The .dev file now looks like this [Project] Libs= Linker=C:\Dev-Cpp\lib\libole32.a_@@_C:\Dev-Cpp\lib\liboleaut32.a_@@_ This also compiles fine. However the dev file now contains full addresses for all libraries. Again this is a portability issue. This may also cause problems with large projects due to shell limitations on the command line length. The correct solution is to only add the library name. This produces the following entry in the .dev file [Project] Libs= Linker=libole32.a_@@_liboleaut32.a _@@_ This is now portable. However is does not compile. The compile log is as follows: Compiler: Default compiler Building Makefile: "C:\Documents and Settings\Steve Higham\My Documents\Dev\ConsoleTest\Makefile.win" Executing make clean rm -f main.o ConsoleTest.exe g++.exe -D__DEBUG__ -c main.cpp -o main.o -I"C:/Dev-Cpp/lib/gcc/mingw32/3.4.2/include" -I"C:/Dev-Cpp/include/c++/3.4.2/backward" -I"C:/Dev-Cpp/include/c++/3.4.2/mingw32" -I"C:/Dev-Cpp/include/c++/3.4.2" -I"C:/Dev-Cpp/include" -g3 g++.exe -D__DEBUG__ main.o -o "ConsoleTest.exe" -L"C:/Dev-Cpp/lib" libole32.a liboleaut32.a -g3 g++.exe: libole32.a: No such file or directory g++.exe: liboleaut32.a: No such file or directory make.exe: *** [ConsoleTest.exe] Error 1 Execution terminated I don't understand why this fails. The -L switch identifies the correct directory (C:/Dev-Cpp/lib) and the lib names are correct. This is the issue. It's probably not the most important issue in the world. But it would be nice to resolve it. Kind Regards, Steve -- Steve Higham › st...@sj... <mailto:st...@sj...> |
|
From: Per W. <pw...@ia...> - 2005-08-11 16:32:20
|
Note that Libs=3D is empty and that the linking is done using the full library name (excluding path). Note that the libraries are not specified with the -l parameter, so gcc will not care about any library paths (-Lxxx). An expected link line should have looked like: gcc ... -L"C:/Dev-Cpp/lib -lole32 -loleaut32 /Per W On Thu, 11 Aug 2005, Steve Higham wrote: > sudhir kumar wrote: > > [Project] > > Libs=3D > > Linker=3Dlibole32.a_@@_liboleaut32.a _@@_ > > This is now portable. However is does not compile. The compile log is as > follows: > > Compiler: Default compiler > > Building Makefile: "C:\Documents and Settings\Steve Higham\My > Documents\Dev\ConsoleTest\Makefile.win" > > Executing make clean > > rm -f main.o ConsoleTest.exe > > g++.exe -D__DEBUG__ -c main.cpp -o main.o > -I"C:/Dev-Cpp/lib/gcc/mingw32/3.4.2/include" > -I"C:/Dev-Cpp/include/c++/3.4.2/backward" > -I"C:/Dev-Cpp/include/c++/3.4.2/mingw32" > -I"C:/Dev-Cpp/include/c++/3.4.2" -I"C:/Dev-Cpp/include" -g3 > > g++.exe -D__DEBUG__ main.o -o "ConsoleTest.exe" -L"C:/Dev-Cpp/lib" > libole32.a liboleaut32.a -g3 > > g++.exe: libole32.a: No such file or directory > > g++.exe: liboleaut32.a: No such file or directory > > make.exe: *** [ConsoleTest.exe] Error 1 > > Execution terminated > > > I don't understand why this fails. The -L switch identifies the correct > directory (C:/Dev-Cpp/lib) and the lib names are correct. This is the iss= ue. > > It's probably not the most important issue in the world. But it would be > nice to resolve it. > > Kind Regards, > > Steve > > -- > > Steve Higham > > =9B st...@sj... <mailto:st...@sj...> |
|
From: Steve H. <st...@sj...> - 2005-08-11 17:19:52
|
Per Westermark wrote: >Note that Libs= is empty and that the linking is done using the full >library name (excluding path). > >Note that the libraries are not specified with the -l parameter, so gcc >will not care about any library paths (-Lxxx). > >An expected link line should have looked like: > >gcc ... -L"C:/Dev-Cpp/lib -lole32 -loleaut32 > >/Per W > >On Thu, 11 Aug 2005, Steve Higham wrote: > > > >>sudhir kumar wrote: >> >>[Project] >> >>Libs= >> >>Linker=libole32.a_@@_liboleaut32.a _@@_ >> >>This is now portable. However is does not compile. The compile log is as >>follows: >> >>Compiler: Default compiler >> >>Building Makefile: "C:\Documents and Settings\Steve Higham\My >>Documents\Dev\ConsoleTest\Makefile.win" >> >>Executing make clean >> >>rm -f main.o ConsoleTest.exe >> >>g++.exe -D__DEBUG__ -c main.cpp -o main.o >>-I"C:/Dev-Cpp/lib/gcc/mingw32/3.4.2/include" >>-I"C:/Dev-Cpp/include/c++/3.4.2/backward" >>-I"C:/Dev-Cpp/include/c++/3.4.2/mingw32" >>-I"C:/Dev-Cpp/include/c++/3.4.2" -I"C:/Dev-Cpp/include" -g3 >> >>g++.exe -D__DEBUG__ main.o -o "ConsoleTest.exe" -L"C:/Dev-Cpp/lib" >>libole32.a liboleaut32.a -g3 >> >>g++.exe: libole32.a: No such file or directory >> >>g++.exe: liboleaut32.a: No such file or directory >> >>make.exe: *** [ConsoleTest.exe] Error 1 >> >>Execution terminated >> >> >>I don't understand why this fails. The -L switch identifies the correct >>directory (C:/Dev-Cpp/lib) and the lib names are correct. This is the issue. >> >>It's probably not the most important issue in the world. But it would be >>nice to resolve it. >> >>Kind Regards, >> >>Steve >> >>-- >> >>Steve Higham >> >>› st...@sj... <mailto:st...@sj...> >> >> > > > > Per, You're quite right. Replacing "C:\Dev-Cpp\lib\libole32.a" with "-lole32" in the Parameters - Linker box has resolved the issue. Many Thanks, Steve -- Steve Higham › st...@sj... <mailto:st...@sj...> |
