<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.2900.5512" name=GENERATOR>
<STYLE>@font-face {
font-family: 宋体;
}
@font-face {
font-family: Verdana;
}
@font-face {
font-family: @宋体;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt 90.0pt; layout-grid: 15.6pt; }
P.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
LI.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
DIV.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; FONT-FAMILY: Verdana; TEXT-DECORATION: none; mso-style-type: personal-compose
}
DIV.Section1 {
page: Section1
}
UNKNOWN {
FONT-SIZE: 10pt
}
BLOCKQUOTE {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>
</HEAD>
<BODY style="FONT-SIZE: 10pt; MARGIN: 10px; FONT-FAMILY: verdana">
<DIV><FONT face=Verdana color=#000080 size=2>thank you for your
reply,</FONT></DIV>
<DIV><FONT color=#000080>now I am confused that besides write makefile with
plugin support in dirver dir, are there other changes? and are there any
changes in our partner's dirver source? IN my opinion, </FONT><FONT
color=#000000>gdal_FOO.dll is just the interface between FOO.DLL and
gdal16.dll, and our partner need provid their dirver as xxx.dll?</FONT></DIV>
<DIV><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080>Best</FONT></DIV>
<DIV><FONT face=Verdana color=#000080 size=2></FONT> </DIV>
<DIV><FONT face=Verdana color=#000080 size=2></FONT> </DIV>
<DIV><FONT face=Verdana color=#c0c0c0 size=2>2009-12-03 </FONT></DIV><FONT
face=Verdana color=#000080 size=2>
<HR style="WIDTH: 100px" align=left color=#b5c4df SIZE=1>
</FONT>
<DIV><FONT face=Verdana color=#c0c0c0 size=2><SPAN>gispowerfan</SPAN>
</FONT></DIV>
<HR color=#b5c4df SIZE=1>
<DIV><FONT face=Verdana size=2><STRONG>发件人：</STRONG> Even Rouault </FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>发送时间：</STRONG> 2009-11-23 02:17:27
</FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>收件人：</STRONG> gispowerfan </FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>抄送：</STRONG> gdal-dev </FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>主题：</STRONG> Re: [gdal-dev] driver
question? </FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT> </DIV>
<DIV><FONT face=Verdana size=2>
<DIV>The best solution would be that your partner delivers to you its driver </DIV>
<DIV>A compiled as a separate GDAL plugin (for example, if the driver </DIV>
<DIV>shortname is FOO : gdal_FOO.dll with an entry point GDALRegister_FOO()). </DIV>
<DIV>You then just have to define GDAL_DRIVER_PATH to point to the directory </DIV>
<DIV>where gdal_FOO.dll is. Be careful : you and your partner must use use </DIV>
<DIV>the same major GDAL version (identical X if GDAL version is 1.X.Y) to </DIV>
<DIV>compile & run against, otherwise there is a risk of C++ ABI </DIV>
<DIV>incompatibility. As far as your driver B is concerned, compiling it as a </DIV>
<DIV>plugin or fully integrated in your GDAL source tree is just a matter of </DIV>
<DIV>conveniency.</DIV>
<DIV></DIV>
<DIV>See http://trac.osgeo.org/gdal/browser/trunk/gdal/frmts/hdf5/makefile.vc </DIV>
<DIV>for an example of a makefile with a plugin target.</DIV>
<DIV></DIV>
<DIV>gispowerfan a écrit :</DIV>
<DIV>> Hi</DIV>
<DIV>> </DIV>
<DIV>> I want to ask a question about how to implement the driver </DIV>
<DIV>> for gdal. Because the partner don't provide their driver source(driver </DIV>
<DIV>> A) for gdal, but we need it and we have our own drivers(driver b) for </DIV>
<DIV>> gdal. So the easy way is that we provide the source contain driver B </DIV>
<DIV>> to our partner, and out partner add their source, then compile it, </DIV>
<DIV>> give us the final dll. Now the question is that we need upate our </DIV>
<DIV>> source frequently, are there other method? is if feasible that our </DIV>
<DIV>> partner change their souce code and put the implement code into *.lib </DIV>
<DIV>> and *.dll, just interface of driver A in frmts driver source?</DIV>
<DIV>> </DIV>
<DIV>> Best regards</DIV>
<DIV>> </DIV>
<DIV>> 2009-11-23</DIV>
<DIV>> ------------------------------------------------------------------------</DIV>
<DIV>> gispowerfan</DIV>
<DIV>> ------------------------------------------------------------------------</DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> gdal-dev mailing list</DIV>
<DIV>> gdal-dev@lists.osgeo.org</DIV>
<DIV>> http://lists.osgeo.org/mailman/listinfo/gdal-dev</DIV>
<DIV></DIV>
<DIV></DIV></FONT></DIV></BODY></HTML>