Author Topic: paths wrong when importing MSWorkspaces  (Read 18347 times)

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: paths wrong when importing MSWorkspaces
« Reply #15 on: September 25, 2005, 08:19:36 pm »
Re-run ./bootstrap
Be patient!
This bug will be fixed soon...

Offline st3vie

  • Multiple posting newcomer
  • *
  • Posts: 41
Re: paths wrong when importing MSWorkspaces
« Reply #16 on: September 25, 2005, 09:48:43 pm »
boot strap goes fine. but during configure i still get this message:

Code
config.status: error: cannot find input file: src/plugins/contrib/Makefile.in

i read in an other thread that a file was missing, so i guess that will solve this then when the cvs is up to date?

-st3vie
« Last Edit: September 25, 2005, 11:33:07 pm by st3vie »

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: paths wrong when importing MSWorkspaces
« Reply #17 on: September 25, 2005, 09:49:50 pm »
Yes, sorry about that.
Be patient!
This bug will be fixed soon...

Offline st3vie

  • Multiple posting newcomer
  • *
  • Posts: 41
Re: paths wrong when importing MSWorkspaces
« Reply #18 on: September 25, 2005, 11:32:29 pm »
to go back on topic here... the importing now went fine. thanks for fixing that. :)

however... i tried it out with the virtualdub sources as well, and when i close CB, it crashed while closing all projects in the workspace one by one.

In the CB Debug messages i see this:
Code
C++ Parser freed
Setting up compiler environment

Some times i see those lines 2 times before it crashes, and some times i see them 10 times (once for every project freed i guess) before it crashes with the message: "Something has gone wrong inside CB and it will...".

-st3vie

grv575

  • Guest
Re: paths wrong when importing MSWorkspaces
« Reply #19 on: September 26, 2005, 12:31:54 am »
codeblocks generates a codeblocks.rpt crash report when it crashes.  posting that would help pin down the source of the crash (note also the codeblocks compiled in the devel directory contains debuggins information while the one in the output directory does not).

zieQ

  • Guest
Re: paths wrong when importing MSWorkspaces
« Reply #20 on: September 26, 2005, 11:09:44 am »
I have located another problem with importers that do not properly handle workspace/project configurations (there's an error on the debug log !). I'm working on a fix but it's quite hard to handle visual 6 workspaces since there's no documentation about the format. I'm trying to figure out how visual 7 imports visual 6 projects configurations. Hope this time the importer will work properly :roll:. Note that, for now, there's no "project configurations" feature in C::B so we fake by using targets instead.

I'll try to post a patch this evening.

Offline st3vie

  • Multiple posting newcomer
  • *
  • Posts: 41
Re: paths wrong when importing MSWorkspaces
« Reply #21 on: September 26, 2005, 12:15:41 pm »
codeblocks generates a codeblocks.rpt crash report when it crashes.  posting that would help pin down the source of the crash (note also the codeblocks compiled in the devel directory contains debuggins information while the one in the output directory does not).

hm, i don't get a .rpt file when that crash occurs. Where should this file be, if it exists? Using find didn't help either. :? Or is this a dev-cvs-only thing you talk about?

@zieQ:
yes, i saw it now as well: ERROR: could not find targets.
i guess i didn't scroll down completely last time, when the import worked. :oops:

-st3vie

zieQ

  • Guest
Re: paths wrong when importing MSWorkspaces
« Reply #22 on: September 26, 2005, 04:39:10 pm »
The rpt file should be located in the same directory as codeblocks executable, so either in the devel/ or output/ directory

Offline st3vie

  • Multiple posting newcomer
  • *
  • Posts: 41
Re: paths wrong when importing MSWorkspaces
« Reply #23 on: September 26, 2005, 06:41:53 pm »
i'm a bit confused now :? The devel and output dir are not there, where i installed CB.
i installed CB in /opt/codeblocks-cvs and this is what i have there:

Code
bin:
codeblocks  console_runner

lib:
libcodeblocks.la  libcodeblocks.so.0      libwxscintilla.la  libwxscintilla.so.0      pkgconfig
libcodeblocks.so  libcodeblocks.so.0.0.1  libwxscintilla.so  libwxscintilla.so.0.0.1

share:
application-registry  applications  codeblocks  icons  mime  mime-info  pixmaps

so.. did i miss something? or do something wrong? Should those dirs have been created during install?

-st3vie

zieQ

  • Guest
Re: paths wrong when importing MSWorkspaces
« Reply #24 on: September 26, 2005, 10:58:07 pm »
Oh hum, I'm not sure how C::B is organised now due to the new autoconf project. Don't know where you could find the rpt file  :?

I fixed the ERROR during import, should be OK now :wink:

Offline st3vie

  • Multiple posting newcomer
  • *
  • Posts: 41
Re: paths wrong when importing MSWorkspaces
« Reply #25 on: September 26, 2005, 11:27:21 pm »
great! :)

about the rpt file... could it be that there now is a dir or two missing, so the rpt file isn't created?

-st3vie

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Re: paths wrong when importing MSWorkspaces
« Reply #26 on: September 27, 2005, 01:15:37 am »
Guys, are you sure the rpt can be created under Linux? I thought it was a windows-only feature. Or maybe I'm wrong?  :? Yiannis?

grv575

  • Guest
Re: paths wrong when importing MSWorkspaces
« Reply #27 on: September 27, 2005, 03:39:43 am »
I was being dumb.  Linux does core dumps, windows does debugger hooks.

Offline st3vie

  • Multiple posting newcomer
  • *
  • Posts: 41
Re: paths wrong when importing MSWorkspaces
« Reply #28 on: September 27, 2005, 12:34:02 pm »
ok, then i can stop looking for faults here. :)

-st3vie

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: paths wrong when importing MSWorkspaces
« Reply #29 on: September 28, 2005, 01:14:19 pm »
@st3vie: I moved your last post here.
Next time, please start a new topic for new issues...
Be patient!
This bug will be fixed soon...