Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

C::B Profiler : new version released!

<< < (4/4)

Zlika:
I have seen 2 little problems:
-The .cbp file format must have been changed in the new version (I still use the 1.0-RC1.1) because the "Code::Blocks_project_file" tag has been changed to "CodeBlocks_project_file" in the cbprofiler.cbp and so the 1.0-RC1.1 can't open it.
- You have renamed the zip resource file cb_profiler.zip to profiler.zip, but you haven't change it in cbprofiler.unix.cbp

And same problem as codestat with extra empty lines (What?!! You don't use C::B to do the job!! :shock:  :mrgreen: )

Zlika

mandrav:

--- Quote from: Zlika on September 25, 2005, 06:53:23 pm ---I have seen 2 little problems:
-The .cbp file format must have been changed in the new version (I still use the 1.0-RC1.1) because the "Code::Blocks_project_file" tag has been changed to "CodeBlocks_project_file" in the cbprofiler.cbp and so the 1.0-RC1.1 can't open it.
- You have renamed the zip resource file cb_profiler.zip to profiler.zip, but you haven't change it in cbprofiler.unix.cbp

And same problem as codestat with extra empty lines (What?!! You don't use C::B to do the job!! :shock:  :mrgreen: )

Zlika

--- End quote ---

1) Yes the project file format has changed subtly to be XML-compliant...
2) I didn't use cbprofiler.unix.cbp so I haven't update it.

You 're maintaining them now. Update whatever is needed...

tiwag:
i just built and tried the profiler-plugin and found, that it doesn't handle custom-variables .

i'm used to parametrize my CB project files with custom variables
like you can see in this excerpt:

--- Code: ---<Build>
    <Target title="Debug Dll">
        <Option output="$(OUTNAME)_d_dll.exe"/>
        <Option working_dir="."/>
        <Option object_output="$(OUTNAME)_d_dll"/>
--- End code ---

the profile file gmon.out is there but the profiler-plugin wants to open a $(OUTNAME)...file which leads to the failure
$(OUTNAME)_d_dll.exe: No such file or directory

when i afterwards change the target's output file-name to the one which equals to the expanded custom variable, the profiler plugin shows the profiled data fine.

used for this test: C::B CVS HEAD 05.10.04, wxMSW261

Zlika:
Well, it's a bug!  :P
I'll try to fix it as soon as possible.

Zlika

Navigation

[0] Message Index

[*] Previous page