Re: Building PHP, questions

From: Date: Thu, 13 Mar 2014 18:52:54 +0000
Subject: Re: Building PHP, questions
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
Hi,

On Thu, March 13, 2014 19:15, Kevin Ingwersen wrote:
> The thing is, that the build itself cant run buildconf or configure, so I
>  have to „port“ the libphp5 part to the build system I am using. With
I think you could run configure & make from your build system and link
against .so or static. That were the easiest way. Otherwise you'll
probably need to sort out all the needed stuff manually (files, headers,
preprocessor, etc.)

> minimal, I just mean to have a runnable scripting engine. Basicaly, i want
> to rebuild what you get when using —disable-all —enable-static
> —enable-embed.
> How far is TSMRC a dependency of PHP actually? I might actually need the
> thread sefety, so I bet i should compile that in in any case. Am 13.03.2014
> um 18:15 schrieb Johannes Schlüter <[email protected]>:
>
>> On Thu, 2014-03-13 at 17:52 +0100, Kevin Ingwersen wrote:
>>
>>> Hey there.
>>>
>>>
>>> For a project I am working on,I want to implement a minimal version
>>> of PHP - really, just it and a very tiny subset of modules. Its for
>>>
>>
>> Define minimal.
>> cd Zend && ./buildconf && configure && make combined with one or
>> two
>> trivial patches to get rid of TSRM dependencies gives you a standalone
>> library containing only the engine. The result of configure
>> --disable-all in the php source is the minimum useful thing.
>>
>>
>>> embeding PHP at the end. I can tell that I need to compile realyl
>>> everything from main and TSRM. But what other fiels do I need to
>>> compile - AND generate? I know I have to generate config.h - but what
>>>  does it depend on?
>>
>> The ones referenced from the current build system's Makefile. I doubt
>> anybody keeps an extra list. Mind that i.e. TSRM becomes quite small in
>> non-tsrm mode.
>>
>>> I am not going to be able to use Autotools - because I am porting it
>>> into a build system I am contributing to.
>>
>> Why? You can always build PHP as a library using --enable-embed (add
>> "=static" if you want it to be a static library) and use that from your
>> other project, yes this adds a dependency but avoids lots of build
>> issues.
>>
>> johannes
>>
>>
>>
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
>

Regards

Anatol



Thread (9 messages)

« previous php.internals (#73117) next »