Note that the Windows environment doesn't support infinitely long command
lines, so especially a link line might fail miserably. This is one of the
reasons why most MS-DOS and Windows compilers supports response files,
where all information from the command line is witten to a text file, and
the compiler tool is called with @response_file on the command line.
When writing own make files, it helps to put object files in a separate
directory, since then it's possible to just specify *.obj (or in this case
*.o) in the link step.
/Per W
On Thu, 2 Jan 2003, Thomas Borrvall wrote:
> Hi again,
>
> thanks for your reply Abhijit. I checked the tabs that you suggested but
> could not see anything wrong with them. As you say, the funny thing is
> that it only happens occasionally. What worries me is that I have the
> source in a system of directories and have since a long time ago adopted
> the style of having long filenames for the sake of clarity. For
> instance, a file is called
> "Source2D/RESTRICTION/DesignToInterpolationMap_2D.cpp". Could this be a
> problem if many such files (say about 50) are included in the project,
> do you think? Perhaps this is what you suggested in your reply, I have
> however installed DEV-C++ in the directory D:\Program\DEV-CPP so this
> should not cause the problem I would think. I notice that the makefile
> grows very much with the long filenames and has very long lines because
> of this.
>
> Bye for now,
>
> Thom
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>
|
