reactos/posix/server/Makefile

# $Id: Makefile,v 1.2 2002/06/08 16:28:04 ea Exp $
#
# ReactOS POSIX+ Environment Subsystem
#
PATH_TO_TOP=../../reactos

TARGET_TYPE = program

TARGET_PATH = misc

TARGET_NAME = psxss

TARGET_APPTYPE = console

TARGET_SDKLIBS = ntdll.a kernel32.a

TARGET_CFLAGS=-Iinclude -I../include -D__PSXSS_ON_W32__

PSXSS_MISC_OBJECTS = \
	misc/main.o \
	misc/init.o \
	misc/print.o

PSXSS_OB_OBJECTS = \
	ob/process.o \
	ob/session.o \
	ob/terminal.o

PSXSS_PORT_OBJECTS = \
	port/api.o \
	port/sbapi.o \
	port/session.o \
	port/utils.o

PSXSS_CALL_OBJECTS = \
	call/null.o \
	call/_exit.o \
	call/stubs.o \
	call/syscall.o

TARGET_OBJECTS=\
	$(PSXSS_MISC_OBJECTS) \
	$(PSXSS_OB_OBJECTS) \
	$(PSXSS_PORT_OBJECTS) \
	$(PSXSS_CALL_OBJECTS)

include $(PATH_TO_TOP)/rules.mak

include $(TOOLS_PATH)/helper.mk

# EOF
Mostly path fixing after new modules layout is in effect. I renamed the terminal emulator CSRTERM: now it is named POSIXW32, because it is a a door to reach the POSIX+ subsystem FROM the Win32 subsystem. svn path=/trunk/; revision=3026 2002-06-08 16:28:05 +00:00			`# $Id: Makefile,v 1.2 2002/06/08 16:28:04 ea Exp $`
PSX: early code for the PSXSS server program. Currently it is a W32 console application, therefore it is not a proper subsystem, but it will be converted to native as soon as it begins working. It probably does NOT work under ROS. I tested it under NT 4.0 SP 6a. To see what it creates in the system name sapce, run WinObj, and HandleEx. If you run csrterm.exe, it tries to connect to psxss.exe, but then dies because the API to tell psxss to create a PSX process it not implemented yet. PSXDLL.DLL will connect to \POSIX+\ApiPort (initial code in psx/lib/psxdll/misc/init.c is mute). svn path=/trunk/; revision=2841 2002-04-10 21:30:22 +00:00			`#`
			`# ReactOS POSIX+ Environment Subsystem`
			`#`
Mostly path fixing after new modules layout is in effect. I renamed the terminal emulator CSRTERM: now it is named POSIXW32, because it is a a door to reach the POSIX+ subsystem FROM the Win32 subsystem. svn path=/trunk/; revision=3026 2002-06-08 16:28:05 +00:00			`PATH_TO_TOP=../../reactos`
PSX: early code for the PSXSS server program. Currently it is a W32 console application, therefore it is not a proper subsystem, but it will be converted to native as soon as it begins working. It probably does NOT work under ROS. I tested it under NT 4.0 SP 6a. To see what it creates in the system name sapce, run WinObj, and HandleEx. If you run csrterm.exe, it tries to connect to psxss.exe, but then dies because the API to tell psxss to create a PSX process it not implemented yet. PSXDLL.DLL will connect to \POSIX+\ApiPort (initial code in psx/lib/psxdll/misc/init.c is mute). svn path=/trunk/; revision=2841 2002-04-10 21:30:22 +00:00
			`TARGET_TYPE = program`

			`TARGET_PATH = misc`

			`TARGET_NAME = psxss`

			`TARGET_APPTYPE = console`

			`TARGET_SDKLIBS = ntdll.a kernel32.a`

			`TARGET_CFLAGS=-Iinclude -I../include -D__PSXSS_ON_W32__`

			`PSXSS_MISC_OBJECTS = \`
			`misc/main.o \`
			`misc/init.o \`
			`misc/print.o`

			`PSXSS_OB_OBJECTS = \`
			`ob/process.o \`
			`ob/session.o \`
			`ob/terminal.o`

			`PSXSS_PORT_OBJECTS = \`
			`port/api.o \`
			`port/sbapi.o \`
			`port/session.o \`
			`port/utils.o`

			`PSXSS_CALL_OBJECTS = \`
			`call/null.o \`
			`call/_exit.o \`
			`call/stubs.o \`
			`call/syscall.o`

			`TARGET_OBJECTS=\`
			`$(PSXSS_MISC_OBJECTS) \`
			`$(PSXSS_OB_OBJECTS) \`
			`$(PSXSS_PORT_OBJECTS) \`
			`$(PSXSS_CALL_OBJECTS)`

			`include $(PATH_TO_TOP)/rules.mak`

			`include $(TOOLS_PATH)/helper.mk`

			`# EOF`