[webkit-dev] Re: Some basic problems during linux port

André-John Mas ajmas at sympatico.ca
Sun Feb 26 10:00:14 PST 2006

IMHO, this certainly sounds like an idea, since Javascript is not  
really necessary for
solutions which are just looking for a rendering solution.

In many ways since Javascript is refered by a mime-type ( text/ 
javascript ) and URL
( javascript: ), it can be seens as an extension, and therefore not a  
dependency, even if it is a most commonly used dependency. Maybe a  
notion a 'plugin'
that is actually specified iat compile time, rather than runtime.  
Then when we compile
we can simply surround it with an #IFDEF that can ommit the  
dependency, if needed.

Note: I have not looked at the source, so I may be suggesting some  
things that are
already there.


On 26-Feb-06, at 12:14 , Mike Emmel wrote:

> After more testing I realized the problem was I was picking up
> config.h from JavaScriptCore
> oops.
> It would be nice if you can build without and install this is one
> problem and the other is the
> Forwarding headers don't include the subdirs in the header path if
> JavaScriptCore was stripped it would work to by providing full include
> paths.
> Mike
> On 2/24/06, Mike Emmel <mike.emmel at gmail.com> wrote:
>> I've run into a few basic things that don't work mainly on gcc  
>> 4.0  on linux.
>> Using #define for namespaces are not expanded
>> Using #define inside template instatiation is not expanded.
>> Now the the defines seem to be temporary for use during code  
>> moving so
>> I'm removing them
>> a bit of drug work but it actually is helping me indentify system  
>> code
>> vs portable.
>> I get the feeling that code in the WebCore namespace should just work
>> on any platform is this correct ?
>> Mike
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at opendarwin.org
> http://www.opendarwin.org/mailman/listinfo/webkit-dev

More information about the webkit-dev mailing list