[asterisk-bugs] [JIRA] (ASTERISK-27728) [patch] BuildSystem: Add NetBSD.

[Alexander Traud (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-27728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Traud updated ASTERISK-27728:
---------------------------------------

    Attachment: NetBSD_configure_flags.patch

> [patch] BuildSystem: Add NetBSD.
> --------------------------------
>
>                 Key: ASTERISK-27728
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27728
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Core/BuildSystem
>    Affects Versions: 13.19.2, 15.2.2
>         Environment: NetBSD 7.1.1
>            Reporter: Alexander Traud
>            Severity: Minor
>              Labels: patch
>         Attachments: NetBSD_configure_flags.patch
>
>
> Currently on NetBSD, you have to do
> {code}ftp http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-13-current.tar.gz
> tar -zxf asterisk-*
> cd asterisk-*
> export PKG_PATH="http://cdn.NetBSD.org/pub/pkgsrc/packages/$(uname -s)/$(uname -p)/$(uname -r)/All"
> pkg_add gcc7 gmake pkg-config editline jansson sqlite3 libuuid libxml2 wget mozilla-rootcerts
> mozilla-rootcerts install
> CFLAGS="-I/usr/pkg/include" LDFLAGS="-L/usr/pkg/lib -Wl,-R/usr/pkg/lib" ./configure{code}On NetBSD, added packages are installed in a 'pkg' sub-directory. Consequently, to find external libraries, added by the user, the paths must be known to the Asterisk build system. Like with other BSD based platforms, the CFLAGS and LDFLAGS should be handled by the script {{./configure}} and the {{Makefile}} automatically, so the user does not have to do more than {{./configure}}.
> Actually, this was reported in ASTERISK-11015 already. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)