H X11 For Mac
2021年6月15日Download here: http://gg.gg/v0h3t
This page is archived for historical reasons only. It is no longer maintained and information may not be current.
*H X11 For Mac Download
*H X11 For Mac Os
*X11 For Mac Os X
*H X11 For Mac High Sierra
The XQuartz project is an open-source effort to develop a version of the X.Org X Window System that runs on OS X. Together with supporting libraries and applications, it forms the X11.app that Apple shipped with OS X versions 10.5 through 10.7. LibX11 - Core X11 protocol client library. Documentation for this library can be found in the included man pages, and in the Xlib spec from the specs subdirectory, also available at. I came across this when I was compiling a simple program: #include X11/Xlib.h #include h #include h Display. display; int main display = XOpenDi. The XQuartz project is an open-source effort to develop a version of the X.Org X Window System that runs on OS X. Together with supporting libraries and applications, it forms the X11.app that Apple shipped with OS X versions 10.5 through 10.7. May 02, 2017 Apple created the XQuartz project as a community effort to further develop and support X11 on Mac. The XQuartz project was originally based on the version of X11 included in Mac OS X v10.5. There have since been multiple releases of XQuartz with fixes, support for new features, and additional refinements to the X11 experience.
OpenOffice has become a native Mac OSX application many years ago, so page this is obsolete as it is about the former X11 based build. If you want to build the native version, please have a look at AquaBuild
For historical reasons, there is also Mac OS X Build Instructions of SRC_m71
Note: supported compilers for Mac can be found in Compiler versions used by port maintainers and release engineersH X11 For Mac Download
Other Mac OS X related Wiki pages.
*6Getting OpenOffice.org and External Sources
*7Preparing to Build
*8Building OpenOffice.orgBuilding OpenOffice.org X11 for Mac OS X PPC and Mac OS X x86
Authors: Eric Hoch
Revised 2006-01-23Introduction
These build instructions are based upon milestone 680_m140 and higher.
Due to the nature of a port in progress this document cannot give a general overview of all the current patches necessary to build a specific milestone. To get this information we recommend you to subscribe to our porting mailing list dev@porting.openoffice.org.
There you’ll get all the latest information about patches and everything else related to and needed to port OpenOffice.org to the Mac.Special Thanks
Before we begin let me thank all the people without whom these build instructions would make no sense, the coders who are helping to bring OOo 2.0 to Mac OS X.The coders and supporters behind the Mac port are:RequirementsDetermine the shell you use for compilation
The default shell of a cleanly installed Mac OS X 10.3.x/Mac OS X 10.4.x is bash.If you did an update to 10.3.x or 10.4.x from early versions of Mac OS X while keeping your personal settings you may still use the tcsh shell, the default shell of Mac OS X 10.0 to 10.2.x.
Where necessary this read-me distinguishes between bash and tcsh.
To determine the shell you currently use open Terminal.app and type the following command:
ps -p $$
The output shows you which shell you’re currently using.
-/bin/bash or -bash means you are using bash
-/bin/tcsh or -tcsh means you are using the c-shellGetting OpenOffice.org and External SourcesGetting OpenOffice.org Source from CVS
Once you have X properly installed, it’s time to get the OpenOffice.org sources and other external sources. If you’ve built OpenOffice.org from previous sources and have applied other patches, you will need to start from scratch with a fresh CVS version of the sources.
Download the CVS distribution for SRC680_mXXX (replace XXX by the current milestonenumber):
Note that if your computer is behind a firewall and you’re trying to get the sources from the CVS server, you may need to find a proper way to get it to tunnel through the firewall. The protocol runs on port 2401, and some firewalls will not allow communication on this port.
Attention: We recommend a broadband connection and a not too small amount of volume or time left within your contract since the sources are about 300MB and the checkout could take up to an hour or longer depending on the server load.
For further information on this topic see get the source
To get a second copy of the sources use the following commands within your 680_mXXX directory:Additional software that’s not in the official OpenOffice.org sources
Now that you have the sources it’s time to get the software that is not in the official OOo Source Code Tree.
To install Archive::Zip use the following commands in Terminal.app:
If this is your first installation of a module using CPAN you’re asked to configure the CPAN environment. If you’re not 100% sure what to answer simply accept the default answers.
Note: In some cases using CPAN with Mac OS X is a bit problematic. In this case simply follow the instructions given here on this website http://sial.org/howto/perl/life-with-cpan/macosx/ to solve the problem.
GPC is available here: ftp://ftp.cs.man.ac.uk/pub/toby/gpc/gpc231.tar.Z>
Attention: Direct Link to the download but it’s only a few hundred KB.
Note: You can alternatively use the libart_lgpl library instead of GPC. This requires an additional configure flag (--enable-libart) and a precompiled libart library installed in a standard location, such as /usr/lib.
Since OS X comes with no pkg-config, or to be more specific it’s simply not complete in OS X, you have to install it via fink (http://fink.sourceforge.net), MacPorts (http://www.macports.org) or the gentoo port system (http://www.metadistribution.org/macos/).
If you need cups headers (on Mac OS X 10.3., building reports ’cups.h missing’), then download them from http://ftp.cusoo.org/MacOSX/Utilities/PowerPC/cups_Panther/cups.tar.gz and put the headers to ’/usr/include/cups’.
If you want to compile OpenOffice.org with gtk2 support you have to install gtk2 via your porting_mechanismNote: The most current versions of gkt2 and pkg-config are in about 90% of all cases only available as sources that you need to compile and not as binaries. Please consider this while preparing your mac.
Additional Note for fink users: You need to install both packages gtk2 and gtk2-devel using fink install </package name>
Yes, there are other porting mechanisms out there such as the one of NetBSD or you can get precompiled versions of gtk, gnu_copy and pkg-config via pages like osxgnu but the author of these build instructions has no experiences with these so no recommendation for them here.
Note: If you need help with installing or maintaining packages please contact the project that provides the porting_mechanism.
It’s also possible to compile pkg-config, gnu_copy as part of the gnu-coreutils and gtk2 without fink or Macports. Be aware that in this case you need to resolve the various dependencies yourself. So we recommend using one of the porting mechanisms.
Because OS X does not install X11 by default and up to now you haven’t installed one, now may be the time do so.There are various X for Mac OS X out there e.g. Apple’s X11, XDarwin.org’s XDarwin or simply use your porting_mechanism to install either X.org 6.8.x or Xfree86 >=4.3.For help with your X11 please contact the provider of the package or your porting mechanism project
By default OOo builds an Office Development Kit. This ODK requires you to download the unowinreg.dll from here http://tools.openoffice.org/unowinreg_prebuild/680/.Preparing to BuildAdding gpc to OOo sourcesAdding unowinreg.dll to OOo sources
Copy the downloaded unowinreg.dll to <ooo source directory>/build/external/unowinreg/ Applying PatchesH X11 For Mac Os
To apply a patchcdinto the direcotory for the module which needs to be patched and do a:patch -p0 <path/to/the patch>
Most of the patches use the naming schememodul_(subdirectory_subdirectory_etc)_filetopatch.patch.
Vk saver for mac.
This page is archived for historical reasons only. It is no longer maintained and information may not be current.
*H X11 For Mac Download
*H X11 For Mac Os
*X11 For Mac Os X
*H X11 For Mac High Sierra
The XQuartz project is an open-source effort to develop a version of the X.Org X Window System that runs on OS X. Together with supporting libraries and applications, it forms the X11.app that Apple shipped with OS X versions 10.5 through 10.7. LibX11 - Core X11 protocol client library. Documentation for this library can be found in the included man pages, and in the Xlib spec from the specs subdirectory, also available at. I came across this when I was compiling a simple program: #include X11/Xlib.h #include h #include h Display. display; int main display = XOpenDi. The XQuartz project is an open-source effort to develop a version of the X.Org X Window System that runs on OS X. Together with supporting libraries and applications, it forms the X11.app that Apple shipped with OS X versions 10.5 through 10.7. May 02, 2017 Apple created the XQuartz project as a community effort to further develop and support X11 on Mac. The XQuartz project was originally based on the version of X11 included in Mac OS X v10.5. There have since been multiple releases of XQuartz with fixes, support for new features, and additional refinements to the X11 experience.
OpenOffice has become a native Mac OSX application many years ago, so page this is obsolete as it is about the former X11 based build. If you want to build the native version, please have a look at AquaBuild
For historical reasons, there is also Mac OS X Build Instructions of SRC_m71
Note: supported compilers for Mac can be found in Compiler versions used by port maintainers and release engineersH X11 For Mac Download
Other Mac OS X related Wiki pages.
*6Getting OpenOffice.org and External Sources
*7Preparing to Build
*8Building OpenOffice.orgBuilding OpenOffice.org X11 for Mac OS X PPC and Mac OS X x86
Authors: Eric Hoch
Revised 2006-01-23Introduction
These build instructions are based upon milestone 680_m140 and higher.
Due to the nature of a port in progress this document cannot give a general overview of all the current patches necessary to build a specific milestone. To get this information we recommend you to subscribe to our porting mailing list dev@porting.openoffice.org.
There you’ll get all the latest information about patches and everything else related to and needed to port OpenOffice.org to the Mac.Special Thanks
Before we begin let me thank all the people without whom these build instructions would make no sense, the coders who are helping to bring OOo 2.0 to Mac OS X.The coders and supporters behind the Mac port are:RequirementsDetermine the shell you use for compilation
The default shell of a cleanly installed Mac OS X 10.3.x/Mac OS X 10.4.x is bash.If you did an update to 10.3.x or 10.4.x from early versions of Mac OS X while keeping your personal settings you may still use the tcsh shell, the default shell of Mac OS X 10.0 to 10.2.x.
Where necessary this read-me distinguishes between bash and tcsh.
To determine the shell you currently use open Terminal.app and type the following command:
ps -p $$
The output shows you which shell you’re currently using.
-/bin/bash or -bash means you are using bash
-/bin/tcsh or -tcsh means you are using the c-shellGetting OpenOffice.org and External SourcesGetting OpenOffice.org Source from CVS
Once you have X properly installed, it’s time to get the OpenOffice.org sources and other external sources. If you’ve built OpenOffice.org from previous sources and have applied other patches, you will need to start from scratch with a fresh CVS version of the sources.
Download the CVS distribution for SRC680_mXXX (replace XXX by the current milestonenumber):
Note that if your computer is behind a firewall and you’re trying to get the sources from the CVS server, you may need to find a proper way to get it to tunnel through the firewall. The protocol runs on port 2401, and some firewalls will not allow communication on this port.
Attention: We recommend a broadband connection and a not too small amount of volume or time left within your contract since the sources are about 300MB and the checkout could take up to an hour or longer depending on the server load.
For further information on this topic see get the source
To get a second copy of the sources use the following commands within your 680_mXXX directory:Additional software that’s not in the official OpenOffice.org sources
Now that you have the sources it’s time to get the software that is not in the official OOo Source Code Tree.
To install Archive::Zip use the following commands in Terminal.app:
If this is your first installation of a module using CPAN you’re asked to configure the CPAN environment. If you’re not 100% sure what to answer simply accept the default answers.
Note: In some cases using CPAN with Mac OS X is a bit problematic. In this case simply follow the instructions given here on this website http://sial.org/howto/perl/life-with-cpan/macosx/ to solve the problem.
GPC is available here: ftp://ftp.cs.man.ac.uk/pub/toby/gpc/gpc231.tar.Z>
Attention: Direct Link to the download but it’s only a few hundred KB.
Note: You can alternatively use the libart_lgpl library instead of GPC. This requires an additional configure flag (--enable-libart) and a precompiled libart library installed in a standard location, such as /usr/lib.
Since OS X comes with no pkg-config, or to be more specific it’s simply not complete in OS X, you have to install it via fink (http://fink.sourceforge.net), MacPorts (http://www.macports.org) or the gentoo port system (http://www.metadistribution.org/macos/).
If you need cups headers (on Mac OS X 10.3., building reports ’cups.h missing’), then download them from http://ftp.cusoo.org/MacOSX/Utilities/PowerPC/cups_Panther/cups.tar.gz and put the headers to ’/usr/include/cups’.
If you want to compile OpenOffice.org with gtk2 support you have to install gtk2 via your porting_mechanismNote: The most current versions of gkt2 and pkg-config are in about 90% of all cases only available as sources that you need to compile and not as binaries. Please consider this while preparing your mac.
Additional Note for fink users: You need to install both packages gtk2 and gtk2-devel using fink install </package name>
Yes, there are other porting mechanisms out there such as the one of NetBSD or you can get precompiled versions of gtk, gnu_copy and pkg-config via pages like osxgnu but the author of these build instructions has no experiences with these so no recommendation for them here.
Note: If you need help with installing or maintaining packages please contact the project that provides the porting_mechanism.
It’s also possible to compile pkg-config, gnu_copy as part of the gnu-coreutils and gtk2 without fink or Macports. Be aware that in this case you need to resolve the various dependencies yourself. So we recommend using one of the porting mechanisms.
Because OS X does not install X11 by default and up to now you haven’t installed one, now may be the time do so.There are various X for Mac OS X out there e.g. Apple’s X11, XDarwin.org’s XDarwin or simply use your porting_mechanism to install either X.org 6.8.x or Xfree86 >=4.3.For help with your X11 please contact the provider of the package or your porting mechanism project
By default OOo builds an Office Development Kit. This ODK requires you to download the unowinreg.dll from here http://tools.openoffice.org/unowinreg_prebuild/680/.Preparing to BuildAdding gpc to OOo sourcesAdding unowinreg.dll to OOo sources
Copy the downloaded unowinreg.dll to <ooo source directory>/build/external/unowinreg/ Applying PatchesH X11 For Mac Os
To apply a patchcdinto the direcotory for the module which needs to be patched and do a:patch -p0 <path/to/the patch>
Most of the patches use the naming schememodul_(subdirectory_subdirectory_etc)_filetopatch.patch.
Vk saver for mac.
コメント