C++, Dynamic Link Library, PHP, Programming, Ubuntu Server, Web Server

Membuat Ekstensi PHP pada Web Server Apache Menggunakan Pemrograman C++

instalasi pustaka phpcpp pada sistem operasi ubuntu

buat sebuah file bernama MakeFile

#	Makefile template
#	This is an example Makefile that can be used by anyone who is building
#	his or her own PHP extensions using the PHP-CPP library. 
#	In the top part of this file we have included variables that can be
#	altered to fit your configuration, near the bottom the instructions and
#	dependencies for the compiler are defined. The deeper you get into this
#	file, the less likely it is that you will have to change anything in it.

#	Name of your extension
#	This is the name of your extension. Based on this extension name, the
#	name of the library file (name.so) and the name of the config file (name.ini)
#	are automatically generated

NAME				=	my_extension

#	Php.ini directories
#	In the past, PHP used a single php.ini configuration file. Today, most
#	PHP installations use a conf.d directory that holds a set of config files,
#	one for each extension. Use this variable to specify this directory.

INI_DIR				=	/etc/php5/conf.d

#	The extension dirs
#	This is normally a directory like /usr/lib/php5/20121221 (based on the 
#	PHP version that you use. We make use of the command line 'php-config' 
#	instruction to find out what the extension directory is, you can override
#	this with a different fixed directory

EXTENSION_DIR		=	$(shell php-config --extension-dir)

#	The name of the extension and the name of the .ini file
#	These two variables are based on the name of the extension. We simply add
#	a certain extension to them (.so or .ini)

INI 				=	${NAME}.ini

#	Compiler
#	By default, the GNU C++ compiler is used. If you want to use a different
#	compiler, you can change that here. You can change this for both the 
#	compiler (the program that turns the c++ files into object files) and for
#	the linker (the program that links all object files into the single .so
#	library file. By default, g++ (the GNU C++ compiler) is used for both.

COMPILER			=	g++
LINKER				=	g++

#	Compiler and linker flags
#	This variable holds the flags that are passed to the compiler. By default, 
# 	we include the -O2 flag. This flag tells the compiler to optimize the code, 
#	but it makes debugging more difficult. So if you're debugging your application, 
#	you probably want to remove this -O2 flag. At the same time, you can then 
#	add the -g flag to instruct the compiler to include debug information in
#	the library (but this will make the final libphpcpp.so file much bigger, so
#	you want to leave that flag out on production servers).
#	If your extension depends on other libraries (and it does at least depend on
#	one: the PHP-CPP library), you should update the LINKER_DEPENDENCIES variable
#	with a list of all flags that should be passed to the linker.

COMPILER_FLAGS		=	-Wall -c -O2 -std=c++11 -fpic -o
LINKER_FLAGS		=	-shared

#	Command to remove files, copy files and create directories.
#	I've never encountered a *nix environment in which these commands do not work. 
#	So you can probably leave this as it is

RM					=	rm -f
CP					=	cp -f
MKDIR				=	mkdir -p

#	All source files are simply all *.cpp files found in the current directory
#	A builtin Makefile macro is used to scan the current directory and find 
#	all source files. The object files are all compiled versions of the source
#	file, with the .cpp extension being replaced by .o.

SOURCES				=	$(wildcard *.cpp)
OBJECTS				=	$(SOURCES:%.cpp=%.o)

#	From here the build instructions start

all:					${OBJECTS} ${EXTENSION}


						${COMPILER} ${COMPILER_FLAGS} $@ ${@:%.o=%.cpp}

						${CP} ${INI} ${INI_DIR}

buat sebuah .ini file bernama filename.ini lalu isi dengan script berikut


buat sebuah file bernama filename.cpp lalu isi dengan script berikut

#include <phpcpp.h>
#include <stdlib.h>

Php::Value myFunction()
   return "Hello from extension";

 *  tell the compiler that the get_module is a pure C function
extern "C" {
     *  Function that is called by PHP right after the PHP process
     *  has started, and that returns an address of an internal PHP
     *  strucure with all the details and features of your extension
     *  @return void*   a pointer to an address that is understood by PHP
    PHPCPP_EXPORT void *get_module() 
        // static(!) Php::Extension object that should stay in memory
        // for the entire duration of the process (that's why it's static)
        static Php::Extension extension("my_extension", "1.0");
        // @todo    add your own functions, classes, namespaces to the extension
        // return the extension
        return extension;

buka kembali terminal command line lalu masuk pada direktori tempat dimana script-script diatas disimpan, gunakan kembali perintah make && sudo make install untuk proses kompilasi atau building menjadi ekstensi web server nantinya.

hasil dari proses kompilasi script diatas akan menghasilkan file .so seperti berikut

setelah itu daftarkan file .so yang sudah dibuild sebelumnya pada konfigurasi php.ini,

restart apache dengan perintah sudo service apache2 restart atau sudo /etc/init.d/apache2 restart, kemudian cek status server untuk melihat apakah ekstensi telah terpasang, berikut adalah hasil pemasangan ekstensi pada web server apache, akan muncul pada informasi status server.

Algorithm, C++, Dynamic Link Library, Programming, Visual Studio

Membangun Custom Execution Engine (CEE) Memanfaatkan External Library [Part 2]

Melanjutkan tulisan sebelumnya https://sirojulmiftakh.wordpress.com/2017/03/31/membangun-custom-execution-engine-cee-memanfaatkan-external-library-part-1/ kali ini akan dilanjutkan tentang bagaimana mengintegrasikan pustaka DLL yang telah dibuild sebelumnya. Continue reading “Membangun Custom Execution Engine (CEE) Memanfaatkan External Library [Part 2]”

Algorithm, C++, Dynamic Link Library, Programming, Visual Studio

Membangun Custom Execution Engine (CEE) Memanfaatkan External Library [Part 1]

Terkadang, kita menemukan beberapa aplikasi yang membutuhkan file eksternal seperti pustaka DLL (Dynamic Link Library) untuk menjalankan aplikasinya.

Bagaimana cara membuat eksternal library tersebut?

Pada tulisan ini, akan dilakukan percobaan membuat sebuah pustaka DLL untuk mendukung kebutuhan jalannya sebuah aplikasi.

Kebutuhan percobaan :
– Visual Studio IDE
– C++ Programming Language
– Niat untuk mencoba 🙂 Continue reading “Membangun Custom Execution Engine (CEE) Memanfaatkan External Library [Part 1]”