#88 option to use .o instead of .rel, specify output directory

open
nobody
None
1
2004-11-12
2004-11-12
No

An option to use suffix .o instead of .rel for the object
files would make it easier to use existing Makefiles.

Being able to specify output directories for object or
listing files would be nice too.

Discussion

  • Maarten Brock

    Maarten Brock - 2004-11-29

    Logged In: YES
    user_id=888171

    Doesn't -o do all that? It's even in the manual.

     
  • Frieder Ferlemann

    Logged In: YES
    user_id=589052

    no, not really: this allows you to specify _one_ directory
    or file.
    Some Makefiles assume they can have separate directories
    (/asm /src /obj /lst).

    To the '.o' part of the request: one implicit rule of make is
    to call the c compiler (cc) when its told to get an object
    file (with suffix 'o').
    So some Makefiles don't work without modification of
    the dependencies (otherwise eventually just changing CC,
    CFLAGS, LL and LFLAGS would do).

     
  • Maarten Brock

    Maarten Brock - 2004-11-30

    Logged In: YES
    user_id=888171

    Why would this not work?

    .o: .c
    $(CC) -c $< -o $@

     
  • Vangelis Rokas

    Vangelis Rokas - 2004-12-01

    Logged In: YES
    user_id=770505

    When creating dependencies, sdcpp creates by default rules
    like this:

    foo.rel: foo.c

    For ports like pic16, it would be nice if dependencies
    with .o were created. (foo.o: foo.c)

    Perhaps a command line option is necessery, but it seems
    that the object suffix is hardcoded in sdcpp.

    Vangelis

     
  • Borut Ražem

    Borut Ražem - 2005-11-27

    Logged In: YES
    user_id=568035

    added command line option -obj-ext=<extension> to SDCPP to
    define object file externion, used for generation of make
    dependencies (-M); pass -obj-ext=<extension> to SDCPP.

    Done in sdcc 2.5.4 #1176

    Borut

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks