welcome: please sign in
location: Diff for "PackageOpenBugs"
Differences between revisions 11 and 21 (spanning 10 versions)
Revision 11 as of 2009-12-17 19:55:39
Size: 1561
Editor: NealThomas
Comment:
Revision 21 as of 2011-03-28 18:13:59
Size: 2295
Editor: snthomas99
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

    . '''note: ''' if you have created any [[DevEnvironmentWindowsVsElf|Linux-related binary files]], chances are good that some Windows .ocf files were overwritten by some Linux .ocf files. Therefore, before packaging OpenBUGS for windows distribution, it is a good idea to delete all compiled objects and recompile. for example:

        . {{{
find -name '*.ocf' -o -iname '*.osf' -exec rm -f {} \;
}}}
Line 11: Line 5:
        . Rsrc/Strings.odc         . System/Rsrc/Strings.odc
Line 21: Line 15:

    . '''note: ''' Although not required, it is a good idea to create the linux distribution first. If you have created any [[DevEnvironmentWindowsVsElf|Linux-related binary files]], chances are good that some Windows .ocf files were overwritten by some Linux .ocf files. Therefore, before packaging OpenBUGS for windows distribution, it is a good idea to delete all compiled objects and recompile. for example:

        . {{{
find -iname '*.osf' -o -iname '*.ocf' -exec rm -f {} \;
}}}

    .Before compiling, also check that HostFiles.odc and Kernel.odc in directory lin have been renamed LinHostFiles.odc and LinKernel.odc

    .Developer->Make.odc->DevCompiler.CompileThis
    .Developer->Linking.odc->DevLinker.Link
    .Developer->Linking.odc-> DevPacker.PackThis OpenBUGS.exe
    .Developer->Linking.odc-> DevLinker.LinkDll

    <<BR>>
Line 25: Line 35:
    . '''FIX NEEDED: ''' libOpenBUGS.so is still part of the windows distribution.
Line 27: Line 36:
    . '''For a full release:''' use ftp -i openbugs.info to upload Manuals/*.html from the local c:/OpenBUGS directory. Also upload Developer/*.html to the subdirectory Developer and GeoBUGS/Manuals/*.html to the GeoBUGS subdirectory. A username and password must be obtained from the wiki maintainer to use ftp. Also remember to check Manuals/contents.html before the Copy OpenBUGS step to make sure all section headings are collapsed. Otherwise, some will be 'open' in the distributed .odc and .html versions, which is confusing and ugly.     . '''For a full release:''' use ftp -i openbugs.info to upload Manuals/*.html from the local c:/OpenBUGS directory (do not create a manuals subdirectory on the remote host). The windows ftp app is usually in /windows/system32 if it is not included in the default path. Upload Developer/*.html to the subdirectory Developer (do not create a manuals subdirectory inside of Developer). Also upload GeoBUGS/Manuals/*.html to the GeoBUGS subdirectory and GeoBUGS/Examples/*.html to the Examples subdirectory inside of the GeoBUGS directory, and similarly for ReliaBUGS in the Reliability directory. A username and password must be obtained from the wiki maintainer to use ftp. Also remember to check Manuals/contents.html before the Copy OpenBUGS step to make sure all section headings are collapsed. Otherwise, some will be 'open' in the distributed .odc and .html versions, which is confusing and ugly.

package OpenBUGS for distribution (also generates html files)

  • increment version number in the following files
    • System/Rsrc/Strings.odc
    • Manual/Manual.odc
    • Developer/Manual.odc
    • GeoBUGS/Manuals/Manual.odc
    • Bugs/CLI.odc (see linking ELF shared object)

  • note: Although not required, it is a good idea to create the linux distribution first. If you have created any Linux-related binary files, chances are good that some Windows .ocf files were overwritten by some Linux .ocf files. Therefore, before packaging OpenBUGS for windows distribution, it is a good idea to delete all compiled objects and recompile. for example:

    • find -iname '*.osf' -o -iname '*.ocf' -exec rm -f {} \;
  • Before compiling, also check that HostFiles.odc and Kernel.odc in directory lin have been renamed LinHostFiles.odc and LinKernel.odc

  • Developer->Make.odc->DevCompiler.CompileThis

  • Developer->Linking.odc->DevLinker.Link

  • Developer->Linking.odc-> DevPacker.PackThis OpenBUGS.exe

  • Developer->Linking.odc-> DevLinker.LinkDll


  • close BlackBox entirely and reopen. Make sure no files are open in BlackBox before proceeding to the next step.

  • Dev -> Copy OpenBUGS

  • For a full release: use ftp -i openbugs.info to upload Manuals/*.html from the local c:/OpenBUGS directory (do not create a manuals subdirectory on the remote host). The windows ftp app is usually in /windows/system32 if it is not included in the default path. Upload Developer/*.html to the subdirectory Developer (do not create a manuals subdirectory inside of Developer). Also upload GeoBUGS/Manuals/*.html to the GeoBUGS subdirectory and GeoBUGS/Examples/*.html to the Examples subdirectory inside of the GeoBUGS directory, and similarly for ReliaBUGS in the Reliability directory. A username and password must be obtained from the wiki maintainer to use ftp. Also remember to check Manuals/contents.html before the Copy OpenBUGS step to make sure all section headings are collapsed. Otherwise, some will be 'open' in the distributed .odc and .html versions, which is confusing and ugly.

PackageOpenBugs (last edited 2011-03-28 18:13:59 by snthomas99)