Hi!
> seems like it doesn't like your globals :) could be a problem
> with the way you are building? what do you see when you type
> 'make'? a list of commands might help us sort it out :)
These are my rules and variables for building:
CPPFLAGS=-palmos3.5 -I$(RAZORPATH)/Src -I$(PRJPATH)/Src
-DERROR_CHECK_LEVEL=$(ERROR_CHECK_LEVEL)
CXXFLAGS=-g -fno-rtti -fno-exceptions -$(OPTLEVEL)
CXX=m68k-palmos-g++
#
# Rule definitions
#
$(OBJPATH)/%.o : $(RAZORPATH)/Src/%.cpp
@echo "Compiling $<..." && \
$(CXX) $(CPPFLAGS) $(CXXFLAGS) -o $@ -c $<
#
# Rule for linking the project
#
$(OBJPATH)/$(PRJNAME) : $(OBJS)
@echo "Linking..." && \
m68k-palmos-gcc $(OBJS) -g -o "$@" -lnoexcept
#
# Rule for building PRCFile
#
$(EXECUTABLE) : $(OBJS) $(OBJPATH)/bin.res
@echo "Building program file $(EXECUTABLE)..." && \
cd $(OBJPATH)/ && \
build-prc -o ../$(EXECUTABLE) -n "$(PRJNAME)" -c $(CREATORID) $(PRJNAME) *.bin
> have you thought about using a #define for these constants instead?
>
> #define appCreator 'Razr'
> #define appVersionNum 0x01
>
> thats how i have been doing it since day one.. is there a need to
> store them in a global variable? they are obviously not going to
> change, so might be best to declare as constants :)
The basic idea here was that the Customization.h belongs to a library, and
Customization.cpp belongs to the program which is using
that library. This makes it possible to change parameters of the library w/o
recompiling it.
Cheers,
Tilo
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
