12-30-2016
Without seeing the makefile (and, maybe also seeing some of the source files being processed by those targets) there is no way to give a definitive answer. You assume that exp is an abbreviation of export. I would have made a 1st guess that it was an abbreviation of experimental. Maybe they are for libraries and include files developed by someone with the initials EXP. I'm sure there are lots of other possibilities.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have concatenated 2 makefiles, to produce 1 however it is not running all of the code, producing a fatal error: symbol referencing errors. No output written. Can anybody please help? (4 Replies)
Discussion started by: Dan Rooney
4 Replies
2. UNIX for Dummies Questions & Answers
I need to develop a makefile that spans across directories. For example, let's say i have an upper level directory (main) and about 2 subdirectories. I want my .cpp files and .o files to be in one subdirectory. I want my .a files to be in the other subdirectory. The .a files are made up of the... (0 Replies)
Discussion started by: benjie_asu
0 Replies
3. Shell Programming and Scripting
for example in my make file im building path from env variables and string but need to see what is did
what is the best way to print the result?
say I have in my Makefile :
exec_prefix = $(RUN_ENV_LOCAL)/apache
and I will like to print the exec_prefix value , how can it be done ? (1 Reply)
Discussion started by: umen
1 Replies
4. UNIX for Advanced & Expert Users
Solved........ (0 Replies)
Discussion started by: klam
0 Replies
5. Programming
Hi Frndz,
I am new to the makefile generation.
I have a source code which contains makefiles in each sub-directories.
Previously we have used the entire source code in Dtbuild environment to get the executables. Now have to change the current Dtbuild environment to Linux build... (1 Reply)
Discussion started by: korraag
1 Replies
6. UNIX for Dummies Questions & Answers
This query is regarding the makefiles of linux kernel modules.
I saw at some sites on net it is suggesting to include the following path:
KERNEL_SOURCE := /usr/src/linux...
while at some places it is askibg to include /lib/modules path:
KERNEL_SOURCE := /lib/modules/2.6.27-7-generic/build... (0 Replies)
Discussion started by: rupeshkp728
0 Replies
7. Programming
I have several programs in several directories and want to use make to build the executables. What I have done is to put the main programs in their own directory together with a makefile to build the program. Then I am thinking of having another makefile residing in the directory above so I can run... (1 Reply)
Discussion started by: kristinu
1 Replies
8. Shell Programming and Scripting
I have a make file and want to write some information and am doing
@echo " RAYPK_LIBSRC = $(RAYPK_LIBSRC)"
The line of code produces
RAYPK_LIBSRC = ./source/library/raypk/time.f ./source/library/raypk/model.f ./source/library/raypk/tomo.f ./source/library/raypk/plt.f... (1 Reply)
Discussion started by: kristinu
1 Replies
9. Shell Programming and Scripting
I have several makefiles to build various programs in a software suite (currently 4 programs). I want to create a main Makefile so that I can build everything I need.
Unsure on the way I should proceed, for example using
include fdtc.mk
or calling
$(MAKE) -f ./mk/Makefile nfdtc
Here... (15 Replies)
Discussion started by: kristinu
15 Replies
10. Programming
I am trying to practice to create Makefiles. The goal is to create a makefile such that if a change is made to any of the source code files, the project can be rebuilt by typing make at the command line.
I have the following files:
ac.cc: has include ac.h and pg.h
fr.cc: has main... (8 Replies)
Discussion started by: pintu1228
8 Replies
LEARN ABOUT REDHAT
perlce
PERLCE(1) Perl Programmers Reference Guide PERLCE(1)
Name
Perl for WinCE
Description
This file gives the instructions for building Perl5.6 and above for WinCE. Please read and understand the terms under which this software
is distributed.
Build
This section describes the steps to be performed to build PerlCE.
Tools & SDK
For compiling, you need Microsoft Embedded Visual Tools, my celib-sources, my console-sources and a perl for win32.
Needed source files can be downloaded via: www.rainer-keuchel.de/wince/dirlist.html
Some portions of the makefile need a shell for win32, rm, cp, mv, xmkdir (mkdir with a -p option). It also uses my cecopy program for
copying files to the ce device.
Make
Miniperl is not built. A pre-existent win32 perl is used.
The paths for tools and additional libraries have to be changed in wince/makefile.ce.
Different ce targets can be specified with the TARGET macro.
Before you start, you need to build celib.dll and w32console. See instructions in these packages for building.
In the wince directory, type "nmake -f makefile.ce". This should build perl.exe and perl.dll. For building extension dlls, type "nmake -f
makefile.ce dlls"
When building ext dlls, you get lots of macro redefinition errors. Just ignore them.
For further information, look in the text files in the wince sub-directory.
Acknowledgements
The port for Win32 was used as a reference.
Author
Rainer Keuchel (keuchel@netwave.de)
perl v5.8.0 2003-02-18 PERLCE(1)