<feed xmlns='http://www.w3.org/2005/Atom'>
<title>unit.git/auto/modules, branch 1.13.0</title>
<subtitle>Universal Web Application Server</subtitle>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/unit.git/'/>
<entry>
<title>Python: fixing Python 3.8 build with clang.</title>
<updated>2019-10-23T11:04:29+00:00</updated>
<author>
<name>Max Romanov</name>
<email>max.romanov@nginx.com</email>
</author>
<published>2019-10-23T11:04:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/unit.git/commit/?id=ad518ae6c491308351eaa0d4065c09870d56f9ae'/>
<id>ad518ae6c491308351eaa0d4065c09870d56f9ae</id>
<content type='text'>
Python 3.8 has 'tp_print' field in PyTypeObject struct.  This field is
attributed as deprecated.  So, clang generates warning (which is turned to
error) as a result of initializing this field.  From the other hand, it is
impossible to omit this field in positional initialization.  The solution
is to use designated initializer.

Silencing usage message during configure python.

This is related to #331 issue on GitHub.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Python 3.8 has 'tp_print' field in PyTypeObject struct.  This field is
attributed as deprecated.  So, clang generates warning (which is turned to
error) as a result of initializing this field.  From the other hand, it is
impossible to omit this field in positional initialization.  The solution
is to use designated initializer.

Silencing usage message during configure python.

This is related to #331 issue on GitHub.
</pre>
</div>
</content>
</entry>
<entry>
<title>Python: fixing build for Python 3.8.</title>
<updated>2019-10-22T13:04:30+00:00</updated>
<author>
<name>Max Romanov</name>
<email>max.romanov@nginx.com</email>
</author>
<published>2019-10-22T13:04:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/unit.git/commit/?id=e54f5f3dc8ec281bbc17e4092d168ea32ae099d7'/>
<id>e54f5f3dc8ec281bbc17e4092d168ea32ae099d7</id>
<content type='text'>
Thanks to tonyafanasyev.
This is related to #331 issue on GitHub.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Thanks to tonyafanasyev.
This is related to #331 issue on GitHub.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fixed "make tests" build without preceding "make".</title>
<updated>2019-10-02T16:11:10+00:00</updated>
<author>
<name>Max Romanov</name>
<email>max.romanov@nginx.com</email>
</author>
<published>2019-10-02T16:11:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/unit.git/commit/?id=9b4e45cafcc8f1f74bcfce3071866ee5eab176a5'/>
<id>9b4e45cafcc8f1f74bcfce3071866ee5eab176a5</id>
<content type='text'>
Currently almost all Unit object files depends on generated nxt_version.h.
This patch adds missing dependence and fixes running make with multiple
jobs.

This closes #318 issue on GitHub.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Currently almost all Unit object files depends on generated nxt_version.h.
This patch adds missing dependence and fixes running make with multiple
jobs.

This closes #318 issue on GitHub.
</pre>
</div>
</content>
</entry>
<entry>
<title>Java: introducing websocket support.</title>
<updated>2019-09-05T12:27:32+00:00</updated>
<author>
<name>Max Romanov</name>
<email>max.romanov@nginx.com</email>
</author>
<published>2019-09-05T12:27:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/unit.git/commit/?id=2b8cab1e2478547398ad9c2fe68e025c180cac54'/>
<id>2b8cab1e2478547398ad9c2fe68e025c180cac54</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Introducing websocket support in router and libunit.</title>
<updated>2019-08-20T13:31:53+00:00</updated>
<author>
<name>Max Romanov</name>
<email>max.romanov@nginx.com</email>
</author>
<published>2019-08-20T13:31:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/unit.git/commit/?id=e501c74ddceab86e48c031ca9b5e154f52dcdae0'/>
<id>e501c74ddceab86e48c031ca9b5e154f52dcdae0</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Perl: propagated compile options from perl build.</title>
<updated>2019-07-17T18:17:30+00:00</updated>
<author>
<name>Valentin Bartenev</name>
<email>vbart@nginx.com</email>
</author>
<published>2019-07-17T18:17:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/unit.git/commit/?id=242dc363ced8d244ff296e1c3c8f802b4857fd35'/>
<id>242dc363ced8d244ff296e1c3c8f802b4857fd35</id>
<content type='text'>
Some Perl compile options affects ABI and not using them while compiling
our module resulted in non-working build.

Notably on 32-bit Debian 10, Perl is built with -D_FILE_OFFSET_BITS=64
and our module after being compiled without this option caused segmentation
faults in unexpected places.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Some Perl compile options affects ABI and not using them while compiling
our module resulted in non-working build.

Notably on 32-bit Debian 10, Perl is built with -D_FILE_OFFSET_BITS=64
and our module after being compiled without this option caused segmentation
faults in unexpected places.
</pre>
</div>
</content>
</entry>
<entry>
<title>Perl: removed "--include=" configure option.</title>
<updated>2019-07-17T18:17:30+00:00</updated>
<author>
<name>Valentin Bartenev</name>
<email>vbart@nginx.com</email>
</author>
<published>2019-07-17T18:17:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/unit.git/commit/?id=dbce694d5a9b43009fef894120edd44ad1e59c25'/>
<id>dbce694d5a9b43009fef894120edd44ad1e59c25</id>
<content type='text'>
It's surplus option because the perl executable returns the proper path.

Also the Perl module configure script was cleaned up a bit.
Note that NXT_PERL_LDOPTS already contains the library path.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
It's surplus option because the perl executable returns the proper path.

Also the Perl module configure script was cleaned up a bit.
Note that NXT_PERL_LDOPTS already contains the library path.
</pre>
</div>
</content>
</entry>
<entry>
<title>Introducing Java Servlet Container beta.</title>
<updated>2019-02-28T15:02:42+00:00</updated>
<author>
<name>Max Romanov</name>
<email>max.romanov@gmail.com</email>
</author>
<published>2019-02-28T15:02:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/unit.git/commit/?id=5bfdebb9e4161a689113d73775498949a09d7fb5'/>
<id>5bfdebb9e4161a689113d73775498949a09d7fb5</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Added trailing zero to version string.</title>
<updated>2019-02-27T14:25:28+00:00</updated>
<author>
<name>Valentin Bartenev</name>
<email>vbart@nginx.com</email>
</author>
<published>2019-02-27T14:25:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/unit.git/commit/?id=5c9fe8c3060f8204b143abae6d81ee8363aba060'/>
<id>5c9fe8c3060f8204b143abae6d81ee8363aba060</id>
<content type='text'>
While it looks nicer without zero 3-rd version number, this should
improve interoperability.  Version string can be parsed or used for
sorting.  And it is easier to handle and less confusing when there
is constant number of version parts.

Moreover, NPM also expects version format with 3 parts.
So ".0" has already been used in Node.js module version.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
While it looks nicer without zero 3-rd version number, this should
improve interoperability.  Version string can be parsed or used for
sorting.  And it is easier to handle and less confusing when there
is constant number of version parts.

Moreover, NPM also expects version format with 3 parts.
So ".0" has already been used in Node.js module version.
</pre>
</div>
</content>
</entry>
<entry>
<title>Improvement and unification of version processing in build scripts.</title>
<updated>2019-02-22T13:31:44+00:00</updated>
<author>
<name>Alexander Borisov</name>
<email>alexander.borisov@nginx.com</email>
</author>
<published>2019-02-22T13:31:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/unit.git/commit/?id=608e09e9def182756e2f1650c6f3416b209fbf58'/>
<id>608e09e9def182756e2f1650c6f3416b209fbf58</id>
<content type='text'>
This also eliminates expressions that incompatible with BSD make, thus fixing
installation of Node.js module on FreeBSD (broken by dace60fc4926).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This also eliminates expressions that incompatible with BSD make, thus fixing
installation of Node.js module on FreeBSD (broken by dace60fc4926).
</pre>
</div>
</content>
</entry>
</feed>
