On Wed, Oct 28, 2009 at 9:05 AM, Scott Lawrence <[email protected]>wrote:
> On Wed, 2009-10-28 at 08:38 -0400, M. Ranganathan wrote: > > Hello, > > > > I recently updated the build tree and separated out the sipxrelay > > project. I found that sipxrelay RPM is not being generated so I went > > ahead and added it to dependencies.mak under the sipxecs target. I am > > confused as to the purpose of this target and am not sure if this is > > the right solution. > > The dependencies.mak just exists to control the ordering of the > subproject builds. > > As Dale pointed out, you also have to modify the spec files to Require > the new project in the right places (in this case, probably > sipXproxy.spec and sipxbridge.spec), and modify the files that control > what gets included in the ISO images (ideally, that could be computed > from the Requires, but it isn't yet). > > > If anybody is able to enlighten me on that last step ( i.e. what gets included in the ISO image) I would much appreciate it. I could build the RPM and I declared victory too soon -- it does not appear in the ISO Image. Thanks Ranga -- M. Ranganathan
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
