Summary: | ASTERISK-04841: [post 1.2] patch for easier cross-compiling (and also for realtime preemptive patched kernels) | ||
Reporter: | Per Hallsmark (saxofon) | Labels: | |
Date Opened: | 2005-08-15 11:33:22 | Date Closed: | 2011-06-07 14:03:05 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) zaptel-1.0.9.1.patch | |
Description: | Makefile changed so that it's adapted a bit more to a staging directory, instead of trusting cross-compiled environment to be quite equal to build environment. (and a question, how did it work before with a line like -I /blablabla? :-) if I remember correctly there shouldn't be space inbetween -I and path...) KDIR is set to native kernels source dir (from /lib/modules...../build) only if it is not set when invoked. Include paths are adjusted to always start with $(KDIR). Similar goes for ROOT_PREFIX/INSTALL_PREFIX, where root prefix points out the staging dir and install prefix points out an "offset" to the ordinary /usr/bin etc if so needed. ROOT_PREFIX would then be used for cross-compiling environments to point out the targets filesystem root (could be a mounted usbmemory path or so) INSTALL_PREFIX would be used to get things installed in for example /usr/local/bin etc. This could probably be updated a bit more, not sure I got it all generalized for all purposes and whishes... :-) But hopefully there could be a generalized structure used all over in Makefiles in the asterisk project and its addons, so that a staging install (for targets) could be made as easily as native installs. When CONFIG_PREEMT_RT is set, spinlocks are defined a bit differently so lines like static spinlock_t dlock = SPIN_LOCK_UNLOCKED; is now like #ifdef CONFIG_PREEMPT_RT DEFINE_SPINLOCK(dlock); #else static spinlock_t dlock = SPIN_LOCK_UNLOCKED; #endif Make target clean has been updated for some binaries that wasn't removed. | ||
Comments: | By: Michael Jerris (mikej) 2005-08-16 07:39:09 updates like this need to be developed against CVS head, not the 1.0.x branch. Can you produce a patch against cvs head? By: Michael Jerris (mikej) 2005-08-16 07:39:57 Also, can you confirm your disclaimer status. We will need a disclaimer to include this work, and can not review it until we receive a disclaimer. By: Per Hallsmark (saxofon) 2005-08-16 08:02:21 Sure, I will not be able to do it the nearest days though unfortunally. How do I change disclaimer status? By: Michael Jerris (mikej) 2005-08-23 07:12:21 bug suspended due to no response. Information about disclaimers can be found inthe bug guidelines at bugs.digium.com. Feel free to re-open this bug when you have a patch for head, and have a discalimer filed with digium. Thanks |