News:

When registered with our forums, feel free to send a "here I am" post here to differ human beings from SPAM bots.

Main Menu

paths wrong when importing MSWorkspaces

Started by st3vie, September 23, 2005, 05:47:45 PM

Previous topic - Next topic

mandrav

Be patient!
This bug will be fixed soon...

st3vie

#16
boot strap goes fine. but during configure i still get this message:

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

mandrav

Be patient!
This bug will be fixed soon...

st3vie

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:
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

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

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.

st3vie

Quote from: grv575 on September 26, 2005, 12:31:54 AMcodeblocks 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

The rpt file should be located in the same directory as codeblocks executable, so either in the devel/ or output/ directory

st3vie

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:


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

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:

st3vie

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

rickg22

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

I was being dumb.  Linux does core dumps, windows does debugger hooks.

st3vie

ok, then i can stop looking for faults here. :)

-st3vie

mandrav

@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...