I thought makefiles didn't have extensions (although I could be wrong). What is in the makefiles?
Okay i've got two make files from the source code I'm trying to port.
makefile.in
makefile.am
I used the command
as that is the directory which containss the make files. Then I try...Code:cd "C:\cygwin\TESTPORT\"
I get no reaction from cygwin after that. How come there is no eboot in my projects folder?Code:make
P.S: I fixed the batch file by the way, I didn't forget.
I thought makefiles didn't have extensions (although I could be wrong). What is in the makefiles?
I'm not really sure, here is an example of some code in the larger makefile.in
I'm guessing I'm supposed to combine the two files but I really don't know the process. I've attached the two files so you can check them out personally.Code:Makefile.in generated by automake 1.9.6 from Makefile.am. # @configure_input@ # Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, # 2003, 2004, 2005 Free Software Foundation, Inc. # This Makefile.in is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY, to the extent permitted by law; without # even the implied warranty of MERCHANTABILITY or FITNESS FOR A # PARTICULAR PURPOSE. @SET_MAKE@ srcdir = @srcdir@ top_srcdir = @top_srcdir@ VPATH = @srcdir@ pkgdatadir = $(datadir)/@PACKAGE@ pkglibdir = $(libdir)/@PACKAGE@ pkgincludedir = $(includedir)/@PACKAGE@ top_builddir = . am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd INSTALL = @INSTALL@ install_sh_DATA = $(install_sh) -c -m 644 install_sh_PROGRAM = $(install_sh) -c install_sh_SCRIPT = $(install_sh) -c INSTALL_HEADER = $(INSTALL_DATA) transform = $(program_transform_name) NORMAL_INSTALL = : PRE_INSTALL = : POST_INSTALL = : NORMAL_UNINSTALL = : PRE_UNINSTALL = : POST_UNINSTALL = : build_triplet = @build@ host_triplet = @host@ target_triplet = @target@ DIST_COMMON = README $(am__configure_deps) $(noinst_HEADERS) \ $(srcdir)/Makefile.am $(srcdir)/Makefile.in \ $(srcdir)/config.h.in $(top_srcdir)/bootstrap/civ.in \ $(top_srcdir)/bootstrap/freeciv.spec.in \ $(top_srcdir)/bootstrap/ser.in \ $(top_srcdir)/bootstrap/undep.sh.in $(top_srcdir)/configure \ $(top_srcdir)/intl/Makefile.in ABOUT-NLS AUTHORS COPYING \
Did you actually spend the 4 hours installing the PSPSDK? The same problem you are having occured with me before I discovered that the psptoolchain script must be executed first before compiling anything.
You don't need to know my mental status. You probably don't want to, either.
September 5th, 2005:
Need LocationFree help? Send me a PM!Originally Posted by F34R
The PSPSDK was installed.
I figured it out I had to use the command autogen.sh. That creates a new "makefile". Now trying to compile that into an eboot is my next problem. I type "make" but I cant find an eboot. I downloaded automake-1.9, where do I put it?
Looking at the makefiles, unless the PSP needs a really complicated method of compling, makefiles should on be one file and A LOT shorter if it is a small program.
See if you can find a sample makefile and adhoc that to fit your installation.
Okay i got one make file from that with no extention I'll fiddle with it tonight and edit this post with my results.
edit: make file not compiling into eboot, more work on the source is required![]()
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks