🚀 go-pugleaf

James Birchall wrote:

> Someone dumped a bunch of c code 

In what kind of file(s) is that c code?

> and an .ide file (from v4.x, I think) on me today.

Now that I've never seen an .ide file you could just try to
open it as a project. Didn't you try?

>  Any idea how to get that .IDE project file to open in the latest IDE?

In general that is not a good idea. Only for small projects (two forms
for instance) that will do.

In other cases: start a new project and add all units by hand.

Hans.

The project files for C++ Builder, and BDS 2006 are text files.

The *.IDE project files for the old Borland C++ compilers were class 
instances streamed to disk.

They are not compatible.  You cannot use the *.IDE files with BDS or BCB.

.  Ed

> James Birchall wrote in message
> news:4526ce61@newsgroups.borland.com...
>
> Hey All,
>
> Someone dumped a bunch of c code and an .ide file (from
> v4.x, I think) on me today.  Any idea how to get that .IDE
> project file to open in the latest IDE?

"Ed Mulroy" <dont_email_me@bitbuc.ket> wrote:
>The project files for C++ Builder, and BDS 2006 are text files.
>
>The *.IDE project files for the old Borland C++ compilers were class 
>instances streamed to disk.
>
>They are not compatible.  You cannot use the *.IDE files with BDS or BCB.
>
>.  Ed
>
>> James Birchall wrote in message
>> news:4526ce61@newsgroups.borland.com...
>>
>> Hey All,
>>
>> Someone dumped a bunch of c code and an .ide file (from
>> v4.x, I think) on me today.  Any idea how to get that .IDE
>> project file to open in the latest IDE?
>
>

Thanks guys.  

The problem is that there are a number of compilation units (a quick check finds 5 mains) all tossed together in a common directory and so "adding by hand" is difficult and requires a couple of days of analysis to determine which files go with which.  The .IDE file, I'm told, is an older Turbo C++ file and should contain the relationships between the various .h/.c/.rc files.  

The problem is opening that file and viewing that relationship. 

From there, it's relatively straightforward to import the new files into the proper projects in BDS.

Any help would be appreciated.

- James

James Birchall wrote:

> The problem is opening that file and viewing that relationship. 

You could open the .ide file with wordpad. Wordpad is a very good
tool to investigate binary files.

I expect that you will see the names of the used files.

Hans.

It shouldn't take days or even a day.  Assuming that you end up with only 10 
or so projects then only an hour or two should do it.

You are coming from Borland C++, a very old compiler that did not have the 
VCL.  Instead Borland C++ used OWL (Object Windows Library) and if the code 
uses OWL then you can't build the projects with BDS2006.

Start by opening a command window and changing to the directory in which the 
files are found.

Use grep determine if OWL is used: (-lw below is lower case -LW)
      grep -lw "owl.h" *.cpp *.h

If it finds anything then you are done.  You can't do it with BDS2006.  Go 
find a copy of Borland C++.  Ebay is a good source.  Try to find Borland C++ 
(BC++) of version 4.52 or version 5.02  (Note that due to a quirk not worth 
going into, 4.53 is actually older and not as desirable than 4.52)

If OWL is not an issue then determine which files contain one of main or 
WinMain.
        grep -lw "main" *.c *.cpp
        grep -lw "WinMain" *.c *.cpp

Each of those files will be a project.  Repeat the following for each of the 
files listed:

  Create a unique directory name
       md  1
  Copy the file to the new directory
       copy /v filename.cpp 1\.
  Start the IDE
  Select File|New and double click Console Wizard (may be
    File|New|Other depending upon compiler version)
  If the file contained 'main' then uncheck GUI and if it contained
  'WinMain' then check GUI
  Check Specify Project Source and add the file IN THE NEW DIRECTORY
  Click Ok
  Select File|Save_All and save to the NEW DIRECTORY
  Select Project|Make
  Copy down the names of some of the items reported as not having
    been found
  Switch to the command window
  Search for which files contain those items
      grep -lw "ItemName" *.c *.cpp *.rc *.def
  Copy the files found to the NEW DIRECTORY
      note that you should not 'move' them as some files might
      be used in more than one project
  Switch back to the IDE and add them with Project|Add_to_project
    making sure that you added them from the NEW DIRECTORY and
    not from the original one

.  Ed

> James Birchall wrote in message
> news:452bbfd0$1@newsgroups.borland.com...
>
> The problem is that there are a number of compilation units
> (a quick check finds 5 mains) all tossed together in a common
> directory and so "adding by hand" is difficult and requires a
> couple of days of analysis to determine which files go with which.
> The .IDE file, I'm told, is an older Turbo C++ file and should
> contain the relationships between the various .h/.c/.rc files.
>
> The problem is opening that file and viewing that relationship.
>
> From there, it's relatively straightforward to import the new files
> into the proper projects in BDS.
>
> Any help would be appreciated.