[Dev] Streamlining development outside of chandler dir, including debugging native code

[Heikki Toivonen]

The apps team at least is finding the need for an easy solution to be 
able to debug native code. My suggestion for this is to do a full build 
when you need that. (make install build may work in some case if you 
have the exact same compiler etc. as the official build machine?)

There have been reports that doing a full build is still hard. Aparna 
has documented her experience, and we will update the instructions based 
on that. Also, we will be setting up new tinderbox machines that report 
the status of full builds.

When you actually need to change some native code, it is currently quite 
tedious in my opinion, and I filed a new bug to fix that:

http://bugzilla.osafoundation.org/show_bug.cgi?id=1642

However, we have differing views of this - some think this is not a good 
idea and would only want it if it did not affect the current way of 
doing full builds. While that would seem to offer middle ground, I see 
that as an added complexity in the build system that I would not want to 
maintain.


I hereby declare discussion open regarding all these issues. Please keep 
the discussion on this list for now, and we will summarize the decisions 
in the bugs if appropriate.

-- 
   Heikki Toivonen


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/dev/attachments/20040727/272cb4dc/signature.bin