This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Query On make File creation

Other Parts Discussed in Thread: TVP5146

Hello, I am working on TI EVM Davinci . I was trying to make video display application working. For that I made my own folder cpoied video_display folder into mine . then I need to change the Makefile in the Video_display folder. there i found XDC path , I am not able to understand what path i should provide there for DMAI. I need to know when it said that dmai_Install_dir/ packages which are thoose pacake laocated and other packages in the make file. so that I can link them in the make file ]

  • an anybody help me , how to add prefix paths for header files in application codes usign MAKE files.

    i mean the make file syntax for adding prefix like 

    -C or -LD

    example syntax will be gr8ly helpful...

    In particular I am asking for IPIPE demo in MV5's PSP dir.

     

  • chaps555 said:

    Hello, I am working on TI EVM Davinci . I was trying to make video display application working. For that I made my own folder cpoied video_display folder into mine . then I need to change the Makefile in the Video_display folder. there i found XDC path , I am not able to understand what path i should provide there for DMAI. I need to know when it said that dmai_Install_dir/ packages which are thoose pacake laocated and other packages in the make file. so that I can link them in the make file ]

    XDCPATHS variable normally points to all directories where "packages" subdirectories are found for your project.  When building your project, the build system will try to find all necessary packages within the directories pointed to by XDCPATHS 

  • Digant Desai said:

    an anybody help me , how to add prefix paths for header files in application codes usign MAKE files.

    i mean the make file syntax for adding prefix like 

    -C or -LD

    example syntax will be gr8ly helpful...

    In particular I am asking for IPIPE demo in MV5's PSP dir.

     

     

    I am not sure if I understand your question, but one normally uses the -I prefix to specify include directories which contain the project's header files.  For example

       -I/home/user/workdfir/lsp/ti-davinci/include

    Let me know if this helps or if you are after something else

  • Here is my application code file - montavista 5 's PSP 's IPIPE example code "ipipe-720p-example.c"

    /*************************************************************************

     * Additional HEADER FILES

     */

    /* Kernel header file, prefix path comes from makefile */

    #include <media/davinci/davinci_vpfe.h>

    #include <media/davinci/ccdc_dm355.h>

    #include <ccdc_dm355.h>

    #include "ipipe_example.h"

    #include <asm/arch/dm355_ipipe.h>

    #include "ipipe_config.h"

    #include "mt9t001_capture.h"

    #include "display.h"

     

    /*******************************************************************************

     

    And they have given the following MAKE file,

    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    # Makefile for IPIPE applications

    CC = $(CROSS_COMPILE)gcc

    IPIPE_VGA_SRCS=ipipe_vga_example.o ipipe_config.o config_table.o display.o mt9t001_capture.o

    IPIPE_480P_SRCS=ipipe_480p_example.o ipipe_config.o config_table.o display.o mt9t001_capture.o

    IPIPE_720P_SRCS=ipipe_720p_example.o ipipe_config.o config_table.o display.o mt9t001_capture.o

    IPIPE_RSZ_SRCS=ipipe_rsz_example.o ipipe_config.o config_table.o display.o tvp5146_capture.o

    IPIPE_1080I_SRCS=ipipe_1080i_example.o ipipe_config.o config_table.o display.o mt9t001_capture.o

     

    all: ipipe_vga_example ipipe_480p_example ipipe_720p_example ipipe_rsz_example ipipe_1080i_example

     

    ipipe_vga_example:$(IPIPE_VGA_SRCS)

    $(CC) -o ipipe_vga_example $^

     

    ipipe_480p_example:$(IPIPE_480P_SRCS)

    $(CC) -o ipipe_480p_example $^

     

    ipipe_720p_example:$(IPIPE_720P_SRCS)

    $(CC) -o ipipe_720p_example $^

     

    ipipe_rsz_example:$(IPIPE_RSZ_SRCS)

    $(CC) -o ipipe_rsz_example $^

     

    ipipe_1080i_example:$(IPIPE_1080I_SRCS)

    $(CC) -o ipipe_1080i_example $^

     

    %.o:%.c

    $(CC) $(CFLAGS) -I $(KDIR) -g -D__DEBUG -c $^

     

    clean:

    rm -f *.o *~ ipipe_vga_example ipipe_480p_example ipipe_720p_example ipipe_rsz_example ipipe_1080i_example

    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    Now my problem is when I compile it using  "make " , it doesnt find above mentioned header files. I know I have to add prefix path for header files in the make file as menioned in apication code.
    Now how can I do this ?? that was my question.
    Can you please guide me , thank u very much :)

  • ah, it appears you are trying to build the ipipe example under

         .../dvsdk_2_00_00_22/PSP_2_00_00_140/examples/dm355/ipipe

    If so, these examples depend on two Makefiles, the project Makefile found under the directory above (which appears very similar to the one you posted) and a top level Makefile found a couple of directories up (path below), which you need to modify to specify the right value (dm355 in this case) for the PLATFORM variable

       .../dvsdk_2_00_00_22/PSP_2_00_00_140/examples

    Then you can simply type make at the top level directory above and it should build all dm355 examples including ipipe.

    Now if you make your own project, it is probrably easier you add it to the top level Makefile as these has definitions (such as path the kernel header files) needed by lower level project Makefiles.  If you notice,  the top level Makefile defines the CFLAGS varaible which includes the path to the header files you need.

       CFLAGS = -Wall -I $(LINUXKERN_INSTALL_DIR)/include

    as I suggested in my previous e-mail, -I is the correct makefile flag, and the path that follows it can be stated explicitly or with the help of variables.  FYI, this is industry standard gmake (GNU Make) nomenclature and not specific to TI.

  • Thank you very much , Now i think I can do this.

    I will get back to u if I make struck in such silly error :)