Summary:	ASTERISK-08257: [patch] compiling and installing asterisk-gui on FreeBSD (6.1)
Reporter:	Paul Belanger (pabelanger)	Labels:
Date Opened:	2006-12-01 11:57:29.000-0600	Date Closed:	2006-12-08 01:00:19.000-0600
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) compile_gui_on_freebsd.patch ( 1) compile_on_freebsd_v2.patch ( 2) compile_on_freebsd.patch
Description:	here is a patch to atleast get ast-gui to compile on FreeBSD.  I have hardcoded OSARCH into tools/Makefile until a developer comments on the best way to figure out our OS during build time. I'm thinking a ./configure script like asterisk, but I'll let somebody else comment on that. ****** ADDITIONAL INFORMATION ****** I'll be adding another patch sometime today to fix the installation path issues on FreeBSD.
Comments:	By: Jason Parker (jparker) 2006-12-01 12:07:00.000-0600 Do you have a disclaimer on file? By: Paul Belanger (pabelanger) 2006-12-01 12:11:28.000-0600 Yes, funny thing tho, there was no checkbox for 'Disclaimer on file' like the other projects on Mantis. PB By: Jason Parker (jparker) 2006-12-01 12:18:47.000-0600 Yeah, I noticed that, and it's been fixed.  Thanks. By: Paul Belanger (pabelanger) 2006-12-01 14:37:57.000-0600 Ok, here is a second patch that will fix the compile issues and install asterisk-gui into /usr/local (usually where application go). I have hardcoded 2 variables: OSARCH prefix we need to decided on how to populate there variables, either by a configure script or by hand. PB By: Jason Parker (jparker) 2006-12-01 15:10:16.000-0600 Did you forget to upload the patch? By: Russell Bryant (russell) 2006-12-01 16:33:29.000-0600 I definitely think that a configure script would be the proper way to handle these issues of setting OSARCH and prefix.  OSARCH would be automatically set, and prefix would have the same defaults we use in Asterisk, which is basically /usr for everything except FreeBSD, where the default is /usr/local.  That way, you can easily change it using ./configure --prefix=/use/this/prefix/please. I'll go ahead and assign this to myself.  I don't mind creating this configure script, as it should be pretty easy to do. By: Paul Belanger (pabelanger) 2006-12-02 21:57:12.000-0600 Sorry for the delay on the update, lost access to the internet for a few days.  Again, will require some re-work once the configure script is released. By: Russell Bryant (russell) 2006-12-06 15:29:11.000-0600 The latest version of chan_zap in Asterisk only includes <zaptel/zaptel.h> for both Linux and FreeBSD.  So, it looks like the newest version of Zaptel on FreeBSD should be installing zaptel.h into a zaptel directory, just like we do on Linux. WIth that said, since the GUI requires Asterisk 1.4, I think it's safe to say that Zaptel 1.4 should be required as well. By: Paul Belanger (pabelanger) 2006-12-06 15:33:00.000-0600 Funny you say that, was about to send a message to the mailing lists about this.  Looks like we will need to get the ports version updated and install zaptel.h under the zaptel directory. Because as it stands now, compiling the asterisk-trunk with the FreeBSD ports version of zaptel fails.. problems with the location of zaptel.h. PB By: Russell Bryant (russell) 2006-12-07 05:51:15.000-0600 I just committed a configure script and some significant changes to the Makefiles for the asterisk gui.  Please take a look and make sure that it all works as expected for you now. By: Paul Belanger (pabelanger) 2006-12-07 09:35:05.000-0600 russell: nice work thanks.  A few minor issues around the DESTDIR variable, and zapscan trying to install if not compiled.  Other than that your patch will help greatly. TY, PB By: Russell Bryant (russell) 2006-12-08 01:00:18.000-0600 Thank you very much for the feedback, and the additional patch!  I have merged your final changes so hopefully this is all good to go now.  As always, let us know as you come across any additional issues.