TODO list for each hardware target can be found as sticky topic in the corresponding forum
Some compiling conventions Some of the packages are being built with flags that are redundant or even detrimental. I've patched these out, tested it, and I'll push the changes with Dimitar's permission. Assuming this is okay, I'd like to enforce some conventions for the future.
|
|
|
Administrator has disabled public posting |
Re: Some compiling conventions I'm not sure whether you meant that you still want to see the patch before I commit it. I've added a few more things to the list anyway.
Regarding the second point, Asterisk is a special case. It does use autoconf but not automake and hence the Makefiles don't use CPPFLAGS. However, you still want to set it to avoid the configure warnings. Until now, we have set ASTCFLAGS and ASTLDFLAGS when running make. This is unnecessary because CFLAGS and LDFLAGS are passed through from configure. But since CPPFLAGS is not used, you still need to pass this through manually. The following does the trick. Code:Before: Although the points I've mentioned affect almost every package, I've only applied the __BLACKFIN__ and -mfdpic changes across the board so far. The rest have only been applied to Asterisk because it is arguably the most important package. I'll continue my clean up in the near future, along with the raft of other improvements I have planned. |
|
|
Administrator has disabled public posting |
- Index
- » Developers
- » General discussions
- » Some compiling conventions
Most Active Users
Board Info
- Board Stats: Total Users: 2587 Total Topics: 299 Total Polls: 1 Total Posts: 1727 Dormant
- User Info: Newest User : user2553 Members Online: 0 Guests Online: 141
- Online There are no members online
- Topic
- New
- Locked
- Sticky
- Active
- New/Active
- New/Locked
- New Sticky
- Locked/Active
- Active/Sticky
- Sticky/Locked
- Sticky/Active/Locked