This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

GNU Make + C166

Good day!

Can I get from C166/EC166 compilers information about all nested includes such as -M, -MM, -MD, -MMD keys for GCC compiler?

If not, I can only use make for rebuild target?

Parents
  • That's exactly what I did. Have a normal makefile first and then add dependency checking.

    I dont have any experience with the EC166 (pre?)compiler. Keil doesn't have an EC166 manual online (anymore?). Does EC166 generate a .o (object) or .c (source) file? The .ic files in your example.

    I use the following file extensions:
    .abs -> the final executable/application/image generated by the linker, see
    http://www.keil.com/support/man/docs/l166/l166_intro.htm
    .o -> compiled .c file
    .c -> C source file
    .a66 -> assembly file
    .dep -> dependency file
    .i -> preprocessor output
    .lst -> list file
    .m66 -> map file

    Don't have alot of time but I'll have a look at your makefile later on. If somebody else hasn't done so already.

    Don't you need a link-step (L66) in your build? Combining the .o files to the final application?

    It's useful to draw a tree-like diagram of the build.

                APP.abs
                   ^
            L166 <.o files>
            [ object files ]
               ^        ^
    C166 <.c files>    EC166 <.cpp files> ??
         ^
    [ .ic files ? ]
    or EC166 <.cpp files> here??
    
    

    The .ABS file can then be converted to .HEX (Intel Hex), .BIN or .S (Motorola S-Record) if needed.

    --
    Joost

Reply
  • That's exactly what I did. Have a normal makefile first and then add dependency checking.

    I dont have any experience with the EC166 (pre?)compiler. Keil doesn't have an EC166 manual online (anymore?). Does EC166 generate a .o (object) or .c (source) file? The .ic files in your example.

    I use the following file extensions:
    .abs -> the final executable/application/image generated by the linker, see
    http://www.keil.com/support/man/docs/l166/l166_intro.htm
    .o -> compiled .c file
    .c -> C source file
    .a66 -> assembly file
    .dep -> dependency file
    .i -> preprocessor output
    .lst -> list file
    .m66 -> map file

    Don't have alot of time but I'll have a look at your makefile later on. If somebody else hasn't done so already.

    Don't you need a link-step (L66) in your build? Combining the .o files to the final application?

    It's useful to draw a tree-like diagram of the build.

                APP.abs
                   ^
            L166 <.o files>
            [ object files ]
               ^        ^
    C166 <.c files>    EC166 <.cpp files> ??
         ^
    [ .ic files ? ]
    or EC166 <.cpp files> here??
    
    

    The .ABS file can then be converted to .HEX (Intel Hex), .BIN or .S (Motorola S-Record) if needed.

    --
    Joost

Children
No data