Using the message list and error marking in a custom build.

[datacart]

Hey,

I am not sure that this belongs here but I feel it has more to do with slick-c than anything else.

I have a custom project that I uses a slick-c macro as its build (Command is a Slick-C macro is checked in the build menu).

Basically what I do is I parse some options that I have and then shell out the build command that works with our build environment. I have custom error parsing enabled that works well with Next Error and Previous Error, but It will not set the error markers or the message list.

Is there something special that I have to do with a custom build command to be able to populate these?

I know that I had to add call_list("_postbuild_", _project_name); to even get error parsing to work, so I am thinking that I need to add other things to get the error markers and message list working also.

Here is the part of my build macro that executes the build command.

Code: [Select]

    activate_build();
    reset_next_error();
    clear_pbuffer();
    concur_command(build_cmd);
    call_list("_postbuild_", _project_name);

Any help would be greatly appreciated.

[datacart]

So is this just not possible?

[chrisant]

If more details are presented it might encourage replies.

Knowing the SE version, which OS, sample build output, and how custom error parsing is configured could be relevant.



(FWIW, this is an excerpt from an article I periodically reread to help me get answers/help faster and more easily; it's a little dated in its language, especially the term "hacker", but it's broadly applicable to any technical field.)

[ehab]

i did something like this before, maybe works for you.

Code: [Select]

   reset_next_error();
   activate_build();
   clear_pbuffer();
   clear_all_error_markers();
   concur_command("thebuildcmd.sh "parameters, false, true, false, true);
   set_error_markers();
   refresh('A');
change the concur_command to suit your needs.