Problems compiling the encode Demo

Alex5208

Hello, i have some problems compiling the encode Demo.

First i tried to change some stuff and i got these errors. I canceled my changes and restored the original file, but if i want to compile the original one, it shows me the same Error.

I thought the error is in the makefile or in the rules.make but i cant see anything wrong in it. All paths look fine to me. The "printf("Buongiorno DaVinci!\n");" Demo didn't show such an error

Console Output
[koa@lapt-dipl ~]$ cd dv*

[koa@lapt-dipl dvsdk_1_30_00_23]$ cd demos

[koa@lapt-dipl demos]$ cd encode

[koa@lapt-dipl encode]$ make

Compiling debug/main.o from main.c..

main.c:29:21: xdc/std.h: Datei oder Verzeichnis nicht gefunden (File or Path not found)

main.c:30:32: ti/sdo/ce/trace/gt.h: Datei oder Verzeichnis nicht gefunden (File or Path not found)

main.c:31:33: ti/sdo/ce/CERuntime.h: Datei oder Verzeichnis nicht gefunden (File or Path not found)

main.c:32:45: ti/sdo/ce/utils/trace/TraceUtil.h: Datei oder Verzeichnis nicht gefunden (File or Path not found)

main.c: In function `main':

main.c:369: Warnung: implizite Deklaration der Funktion »CERuntime_init« (Warning: implizite declaration of function [..])

make: *** [debug/main.o] Error 1

Makefile

# Makefile

#

# ============================================================================

# Copyright (c) Texas Instruments Inc 2007

#

# Use of this software is controlled by the terms and conditions found in the

# license agreement under which this software has been supplied or provided.

# ============================================================================

ROOTDIR = ../..

TARGET = $(notdir $(CURDIR))

include Rules.make

# Comment this out if you want to see full compiler and linker output.

VERBOSE = @

# Where to output configuration files

XDC_CFG = $(TARGET)_config

# Output compiler options

XDC_CFLAGS = $(XDC_CFG)/compiler.opt

# Output linker file

XDC_LFILE = $(XDC_CFG)/linker.cmd

# Input configuration file

XDC_CFGFILE = $(TARGET).cfg

# Target tools

XDC_TARGET = gnu.targets.MVArm9

# Platform (board) to build for

XDC_PLATFORM = ti.platforms.evmDM355

# Package path for the XDC tools

XDC_PATH = ../g711;$(CODEC_INSTALL_DIR)/packages;$(CE_INSTALL_DIR)/packages;$(LINK_INSTALL_DIR)/packages;$(XDAIS_INSTALL_DIR)/packages;$(CMEM_INSTALL_DIR)/packages;$(FC_INSTALL_DIR)/packages

# The XDC configuration tool command line

CONFIGURO = XDCPATH="$(XDC_PATH)" $(XDC_INSTALL_DIR)/xs xdc.tools.configuro

C_FLAGS += -Wall -DDM355 -Dti_sdo_ce_osal_Memory_USEDEPRECATEDAPIS=1

CPP_FLAGS += -I$(DVSDK_INSTALL_DIR)/demos/utils/include \

-I$(LINUXKERNEL_INSTALL_DIR)/include

LD_FLAGS += -lfreetype -lpng -ljpeg -lpthread

COMPILE.c = $(VERBOSE) $(MVTOOL_PREFIX)gcc $(C_FLAGS) $(CPP_FLAGS) -c

LINK.c = $(VERBOSE) $(MVTOOL_PREFIX)gcc $(LD_FLAGS)

DBGTARGET = debug/$(TARGET)d

RELTARGET = release/$(TARGET)

DBGCFLAGS = -g -D__DEBUG

RELCFLAGS = -O2 -fno-strict-aliasing

SOURCES = $(wildcard *.c)

HEADERS = $(wildcard *.h)

DBGOBJFILES = $(SOURCES:%.c=debug/%.o)

RELOBJFILES = $(SOURCES:%.c=release/%.o)

RELLDFLAGS = $(DVSDK_INSTALL_DIR)/demos/utils/lib/simplewidget.a \

$(DVSDK_INSTALL_DIR)/demos/utils/lib/msp430lib.a \

$(DVSDK_INSTALL_DIR)/demos/utils/lib/rszcopy.a \

$(DVSDK_INSTALL_DIR)/demos/utils/lib/smooth.a

DBGLDFLAGS = $(DVSDK_INSTALL_DIR)/demos/utils/lib/simplewidgetd.a \

$(DVSDK_INSTALL_DIR)/demos/utils/lib/msp430libd.a \

$(DVSDK_INSTALL_DIR)/demos/utils/lib/rszcopyd.a \

$(DVSDK_INSTALL_DIR)/demos/utils/lib/smoothd.a

.PHONY: clean debug release install

all: debug release

install:

@echo

@echo Installing $(TARGET) target files to $(EXEC_DIR)..

$(VERBOSE) install -d $(EXEC_DIR)

$(VERBOSE) install $(RELTARGET) $(EXEC_DIR)

$(VERBOSE) install -m 444 $(TARGET).txt $(EXEC_DIR)

release: $(RELTARGET)

@echo

debug: $(DBGTARGET)

@echo

$(RELTARGET): $(RELOBJFILES)

@echo

@echo Linking $@ from $^..

$(LINK.c) -o $@ $^ $(RELLDFLAGS) $(XDC_LFILE)

$(DBGTARGET): $(DBGOBJFILES)

@echo

@echo Linking $@ from $^..

$(LINK.c) -o $@ $^ $(DBGLDFLAGS) $(XDC_LFILE)

$(RELOBJFILES): release/%.o: %.c $(HEADERS) $(XDC_CFLAGS)

@mkdir -p release

@echo Compiling $@ from $<..

$(COMPILE.c) $(RELCFLAGS) $(shell cat $(XDC_CFLAGS)) -o $@ $<

$(DBGOBJFILES): debug/%.o: %.c $(HEADERS) $(XDC_CFLAGS)

@mkdir -p debug

@echo Compiling $@ from $<..

$(COMPILE.c) $(DBGCFLAGS) $(shell cat $(XDC_CFLAGS)) -o $@ $<

$(XDC_LFILE) $(XDC_CFLAGS): $(XDC_CFG)

$(XDC_CFG): $(XDC_CFGFILE)

@echo

@echo ======== Building $(TARGET) ========

@echo Configuring application using $<

@echo

$(CONFIGURO) -c $(MVTOOL_DIR) -o $(XDC_CFG) -t $(XDC_TARGET) -p $(XDC_PLATFORM) $(XDC_CFGFILE)

clean:

@echo Removing generated files..

$(VERBOSE) -$(RM) -rf $(XDC_CFG) release debug *~ *.d .dep

Rules.make

# The installation directory of the DVSDK dvsdk_1_30_00_23.

DVSDK_INSTALL_DIR=/home/koa/dvsdk_1_30_00_23

# For backwards compatibility

DVEVM_INSTALL_DIR=$(DVSDK_INSTALL_DIR)

# Where the Codec Engine package is installed.

CE_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/codec_engine_2_00

# Where the XDAIS package is installed.

XDAIS_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/xdais_6_00

# Where the DSP Link package is installed.

#LINK_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/NOT_USED

# Where the CMEM (contiguous memory allocator) package is installed.

CMEM_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/cmem_2_00

# Where the codec servers are installed

CODEC_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/dm355_codecs_1_06_01

# Where the RTSC tools package is installed.

XDC_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/xdc_3_00_02_11

# Where Framework Components product is installed

FC_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/framework_components_2_00

# Where DSP/BIOS is installed

BIOS_INSTALL_DIR=$(DVSDK_INSTALL_DIR)/

# The directory that points to your kernel source directory.

LINUXKERNEL_INSTALL_DIR=/home/koa/workdir/lsp/ti-davinci

# The prefix to be added before the GNU compiler tools (optionally including

# path), i.e. "arm_v5t_le-" or "/opt/bin/arm_v5t_le-".

MVTOOL_DIR=/opt/mv_pro_4.0.1/montavista/pro/devkit/arm/v5t_le

MVTOOL_PREFIX=$(MVTOOL_DIR)/bin/arm_v5t_le-

# Where to copy the resulting executables and data to (when executing 'make

# install') in a proper file structure. This EXEC_DIR should either be visible

# from the target, or you will have to copy this (whole) directory onto the

# target filesystem.

EXEC_DIR=/home/koa/workdir/filesys/opt/dvsdk

over 16 years ago

0 Juan Gonzales over 16 years ago

TI__Mastermind 37340 points

Have you gone thru Getting Started Guide (GSG) at least once? I did and was able to build all demos just fine. FYI, demos need some libraries that are created by building the entire tree per GSG; if you have not done this step and you try to build an individual demo, build will fail.

[edit] also, if you could send the log in English, we might be able to provide more insight.

0 Bernie Thompson TI over 16 years ago

TI__Mastermind 41665 points

The error definately looks like a pathing issue, but I agree that taking a quick look at your make file it seems valid, I am not sure where else the build process could have broken, as Juan mentions, out of the GSG these should build properly. In any case as a temporary measure you could collect the header files it is missing and put them locally to guarantee they are found for the build.

0 Juan Gonzales over 16 years ago

TI__Mastermind 37340 points

Also, have you moved the demo you are trying to build from its original location? I noticed the makefile defines a relative path (as opposed to full path) and hence moving it without making proper changes to makefile will also cause problems.

Again, I am using the latest DM355 DVSDK (available at www.ti.com/davincisoftwareupdates for registered EVM users) and am able to build all the demos without any issues.

0 Alex5208 over 16 years ago in reply to Juan Gonzales

Intellectual 570 points

ill try it tomorrow i think its 4pm in germany.

I also think its a path problem so cause i can now build an own small OSD programm and i can compile it but i have to collect the different Header Files...

So i will get tomorrow the lates version and do GSG again. Thx so far

0 Alex5208 over 16 years ago in reply to Alex5208

Intellectual 570 points

Hi,

Cause Registering takes some days, i tried to reinstall my version that was shipped with the Board, version 1_30_00_23

I started with step 4.2 of the Getting Started Guid (spruf73.pdf)

4.2 Preparing to Install

i copied everything i should to my hdd

4.3.1 Installing Traget Linux Software

logged in as root and started InstallShield for the 3 *.bin files listened in chapter 4.3.1

changed directory to /opt/mv_pro_4.0.1 and extracted the 3 tar.gz files --> /opt/mv_pro_4.0.1/montavista was created

4.3.2 Installing DVSDK Software

Logged in as User Account "koa"

started dvsdk_dm355_setuplinux_1_30_00_23.bin Installshield and installed to /home/koa/dvsdk_1_30_00_23

executed xdc_setuplinux_3_00_02_11.bin installshield and installed to /home/koa/dvsdk_1_30_00_23/xdc_3_00_02_11

4.3.3 Installing the A/V demo Files

copied and extracted data.tar.gz into /home/koa/dvsdk_1_30_00_23

4.3.4 Exporting NFS for Target Access

i created /home/koa/workdir/filesys sitchted to user root and copied /opt/mv_pro_4.0.1/montavista/pro/devkit/arm/v5t_le/target into /home/koa/workdir/filesys

i did chown -R koa opt

i edited the exportfs file and restarted nfs service

4.3.5 Testing NFS

testing the nfs was successful

4.3.6 boot setup for pal

i used "setenv bootargs console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=192.168.1.9:/home/koa/workdir/filesys,nolock video=dm64xxfb:output=pal mem=116M" (without ")

4.4 setting up build/dev enviroment

logged in as user i edited file .bashrc at directory /home/koa and inserted

'PATH="/opt/mv_pro_4.0.1/montavista/pro/devkit/arm/v5t_le/bin:/opt/mv_pro_4.0.1/montavista/pro/bin:/opt/mv_pro_4.0.1/montavista/common/bin:$PATH"' (without ')

and "source .bashrc" after editing

4.4.1 writing simple program

i see the welcome message ...

4.5 Building new Linuxkernel

everything gone fine, some warnings cause of not used functions but i got my uImage and i was able to boot it via tftp (Step 4.7)

4.6 Rebuilding DVEVM Software

here i got errors!

Editing the Rules.make was not necessary, cause the Paths were already fine.

When i do "Make"

everything is fine until it makes the Encode Demo (Decode Demo one step befor was fine)

It says to me:
Making all in subdirectory encode...

make[2]: Entering directory `/home/koa/dvsdk_1_30_00_23/demos/encode'

Compiling debug/main.o from main.c..

main.c:29:21: xdc/std.h Datei oder Verzeichnis nicht gefunden (in english: File or Path not found)

main.c:30:32: ti/sdo/ce/trace/gt.h: Datei oder Verzeichnis nicht gefunden (in english: File or Path not found)

main.c:31:33: ti/sdo/ce/CERuntime.h: Datei oder Verzeichnis nicht gefunden (in english: File or Path not found)

main.c:32:45: ti/sdo/ce/utils/trace/TraceUtil.h: Datei oder Verzeichnis nicht gefunden (in english: File or Path not found)

main.c: In function `main':

main.c:369: Warnung: implizite Deklaration der Funktion >>CERuntime_init<< (in english: Warning: implicitly declaration of function >>CERuntime_init<<)

make[2]: *** [debug/main.o] Error 1

make[2]: Leaving directory `/home/koa/dvsdk_1_30_00_23/demos/encode'

make[1]: *** [encode] Error 2

make[1]: Leaving directory `/home/koa/dvsdk_1_30_00_23/demos'

make: *** [demos] Error 2

I think there are some/a lot of problems finding the Header Files... But were missed i an entry or something else? I think the Error on Building the hole DVEVM Software is the same Error i got if i want to compile the Encode Demo alone...

0 Juan Gonzales over 16 years ago in reply to Alex5208

TI__Mastermind 37340 points

Alex,

I was looking over your comments on your latest post above; with regards to the comment that "Editing the Rules.make was not necessary, cause the Paths were already fine", you still need to edited to define DVSDK_INSTALL_DIR amongst other things, correct?