Recent Posts

Pages: 1 ... 4 5 6 7 8 [9] 10
81
Development / Re: Guide for building C::B on Linux request due to wiki 502 error
« Last post by AndrewCot on September 10, 2021, 06:11:57 am »
Watch out when build C::B via workspace and/or project file on Linux as some of the project files include references to GTK2 like the following:

               <Add option="`pkg-config gdk-2.0 --cflags`" />
               <Add option="`pkg-config --libs gtk+-2.0`" />

Hope this of some use for the future. Now for me to start working on getting the projects files to build with GTK3.
82
In addition to checking out the GNU page,  I would also suggest you have a look at the following as it goes through setting up a project and compiling a sample program.

http://www.sci.brooklyn.cuny.edu/~goetz/codeblocks/codeblocks-instructions.pdf
83
This is not realy an Code::Blocks question.

https://gcc.gnu.org/projects/cxx-status.html

Tim S.
84
There are C++20 features and libraries that my current CodeBlocks installation [20.03] doesn't have, causing a "no such file or directory" error on those "#include" statements in a third-party header file that my program uses, specifically "stduuid".
[bold]List of those #include statements that causes errors[/bold]
- #include <string_view>
- #include <optional>
- #include <span>
So I'm curious what version of C++ does my C::B installation have, since it also has the MinGW GCC compiler installation shipped with. The version of the compiler btw is 8.1.0.
85
Development / Re: Guide for building C::B on Linux request due to wiki 502 error
« Last post by cacb on September 08, 2021, 07:33:57 pm »
@cacb than you very much for the script.
You're welcome, thanks for the updates on GTK3 packages. I am building under Kubuntu 20.04 and find GTK2 works best in my case, but will be ready for GTK3.

Maintaining such a script is easier than a wiki I guess.
86
General (but related to Code::Blocks) / Re: something about M_PI
« Last post by sodev on September 08, 2021, 04:30:47 pm »
M_PI is not part of the C standard but part of POSIX. Most probably the OP is using GCC and that one is more strict regarding the standard. Using a C standard with GNU extensions does help in that case, e.g. instead of using --std=c11 use --std=gnu11.
87
Development / Re: Guide for building C::B on Linux request due to wiki 502 error
« Last post by AndrewCot on September 08, 2021, 12:27:06 pm »
Small update:

I have installed GCC 11.1.0 and have successfully built C::B with iGCC 11.1.0 and it runs.
88
Attached is the system information collected from Xubuntu 20.04 virtualbox guest using my latest C::B source code that I just successfully compiled under Linux.

If anyone thinks that I should add extra output for Linux that will help in trouble shooting C::B issue please let me know and I will try to add it.
89
Development / Re: Guide for building C::B on Linux request due to wiki 502 error
« Last post by AndrewCot on September 08, 2021, 10:54:52 am »
@cacb than you very much for the script. I used it instead of the WIKI doc as the WIKI was for WxWidget 2.8 and as such was way out of date. I used GTK3. I was able to build and run the SF 12529 trunk code.


I had to add a few more packages from the default xubuntu-20.04.2.0-desktop-amd64.iso install (on Virtualbox using a script) to get it to compile and remove the  --with-wx-config="$WX_CONFIG_FULLPATH" ./configure option as the wxconfig was not in the directory specified, but was in the path.

My updated script is below:
Code
#!/bin/bash

#---- install build essentials for codeblocks with gtk2 and gtk3 ----
sudo apt install -y git
sudo apt install -y cmake
sudo apt install -y build-essential
sudo apt install subversion
sudo apt install -y libhunspell-dev libgamin-dev
sudo apt-get install libboost-system-dev

#-------- install build packages for codeblocks with gtk2 --------
# GTK2 #sudo apt install -y libgtk2.0-dev 

#-------- install build packages for codeblocks with gtk3 --------
sudo apt install -y libgtk-3-devmake
sudo apt install -y libwxgtk3.0-gtk3-0v5 libwxgtk3.0-gtk3-dev

# -----------------------------------------------------------------

#path to wxWidgets configuration scripts
WX_CONFIG_DIR=/usr/local/lib/wx/config

#actual wxWidgets configuration to use
#to see alternatives use: find /usr/local/lib/wx/config/*
WX_CONFIG=gtk3-unicode-3.0
WX_CONFIG_FULLPATH="$WX_CONFIG_DIR/$WX_CONFIG"

#build and install paths
CB_DIR=~/code/codeblocks
CB_BUILD_PATH="$CB_DIR/$WX_CONFIG/build"
CB_INSTALL_PATH="$CB_DIR/$WX_CONFIG/install"

#create build area
mkdir -p "$CB_BUILD_PATH"
pushd    "$CB_BUILD_PATH"
pwd
#git clone https://github.com/obfuscated/codeblocks_sf codeblocks_git
#cd codeblocks_git
svn checkout https://svn.code.sf.net/p/codeblocks/code/trunk codeblocks_sf
cd codeblocks_sf

# -----------------------------------------------------------------

#configure, build & install using selected configuration
./bootstrap
./configure --with-contrib-plugins=all             \
            --prefix="$CB_INSTALL_PATH"
#./configure --with-contrib-plugins=all             \
#            --with-wx-config="$WX_CONFIG_FULLPATH" \
#            --prefix="$CB_INSTALL_PATH"

make
make install
ls -l "$CB_INSTALL_PATH/bin"
popd

Below is the VirtualBox script I use to install the initial XUbuntu and then did an upgrade and ran the script. I hope this may save you time in the future if you need to use VB as it can be modified for Windows very easily as most of the lines are for configuring the Virtualbox common HDD, Network, Video, Sound and serial port settings.


Code
@rem https://kifarunix.com/how-to-automate-virtual-machine-installation-on-virtualbox/

set VM_Name=XUbuntu-2004-CB
set UserName=UNAME
set UserPassword=UPASSWORD
set ISO_IMAGE="%CD%\xubuntu-20.04.2.0-desktop-amd64.iso"

@rem ==============================================================================

set VM_Directory=G:\VirtualBox
set VBoxManageExe="C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"

@rem goto end
@rem goto OS_Install
@echo off
%VBoxManageExe% createvm --name %VM_Name% --ostype Ubuntu_64 --register --basefolder "%VM_Directory%"
%VBoxManageExe% createmedium --filename "%VM_Directory%\%VM_Name%\%VM_Name%.vdi" --format VDI --size 102200

%VBoxManageExe% storagectl %VM_Name% --name SATA --add SATA --controller IntelAhci
%VBoxManageExe% storageattach %VM_Name% --storagectl SATA --port 0 --device 0 --type hdd --medium "%VM_Directory%\%VM_Name%\%VM_Name%.vdi"

%VBoxManageExe% storagectl %VM_Name% --name IDE --add IDE --controller PIIX4
@rem %VBoxManageExe% storageattach %VM_Name% --storagectl IDE --port 0 --device 0 --type dvddrive --medium "none"

%VBoxManageExe% modifyvm %VM_Name% --clipboard-mode bidirectional --draganddrop bidirectional
%VBoxManageExe% modifyvm %VM_Name% --memory 8192 --vram 128
%VBoxManageExe% modifyvm %VM_Name% --graphicscontroller vmsvga --monitorcount 2 --accelerate3d on
%VBoxManageExe% modifyvm %VM_Name% --ioapic on
%VBoxManageExe% modifyvm %VM_Name% --boot1 dvd --boot2 disk --boot3 none --boot4 none
%VBoxManageExe% modifyvm %VM_Name% --cpus 4
%VBoxManageExe% modifyvm %VM_Name% --audio dsound  --audiocontroller hda  --audioin off    --audioout on

%VBoxManageExe% modifyvm %VM_Name% --usb off
%VBoxManageExe% modifyvm %VM_Name% --usbohci off
%VBoxManageExe% modifyvm %VM_Name% --usbehci off
%VBoxManageExe% modifyvm %VM_Name% --usbxhci off

%VBoxManageExe% modifyvm %VM_Name% --nic1 nat --nictype1 82540EM --cableconnected1 on --natpf1 ["EGM Simulator"],tcp,[0.0.0.0],3321,[0.0.0.0],3321

%VBoxManageExe% modifyvm %VM_Name% --nic2 none
%VBoxManageExe% modifyvm %VM_Name% --nic3 none
%VBoxManageExe% modifyvm %VM_Name% --nic4 none

%VBoxManageExe% modifyvm %VM_Name% --uart1 0x3f8 4 --uartmode1 COM1
%VBoxManageExe% modifyvm %VM_Name% --uart2 off
%VBoxManageExe% modifyvm %VM_Name% --uart3 0x3e8 4 --uartmode3 COM3
%VBoxManageExe% modifyvm %VM_Name% --uart4 0x2e8 3 --uartmode4 COM4

%VBoxManageExe% sharedfolder add %VM_Name% --name="VirtualBoxTransfer" --hostpath="%VM_Directory%\VB_Transfer" --automount --auto-mount-point="/home/%UserName%/Transfer"

:OS_Install
@rem  NOTE: A caret at the line end, appends the next line, the first character of the appended line will be escaped.

@echo on
%VBoxManageExe% unattended install "%VM_Name%" --user=%UserName% --password=%UserPassword% --country=AU --time-zone="Australia/Sydney" --hostname="%VM_Name%".myguest.virtualbox.org ^
--iso="%ISO_IMAGE%" --start-vm=gui --install-additions --post-install-command="/home/%UserName%/Transfer/SU_Install_Common_and_GamingMachine.sh"

@rem --additionsIsoPath = C:\Program Files\Oracle\VirtualBox\ VBoxGuestAdditions.iso

@rem does NOT work %VBoxManageExe% guestproperty wait "%VM_Name%" installation_finished
@rem %VBoxManageExe%VBoxManage controlvm "%VM_Name%" acpipowerbutton
@rem %VBoxManageExe%VBoxManage startvm "%VM_Name%"

@rem %VBoxManageExe% --nologo guestcontrol "%VM_Name%" run --exe "usermod -G vboxsf -a ubuntu" --username su --password ubuntu --wait-stdout
@echo.
@echo.
@echo ^+=====================================================================================^+
@echo ^+                                                                                     ^|
@echo ^+  REBOOT THE VM ONCE THE INSTALL FINISHES FOR THE TRASFER DIRECTORY MAPPING TO SETUP ^|
@echo ^+                                                                                     ^|
@echo ^+=====================================================================================^+
@echo ^+                                                                                     ^|
@echo ^+  After the reboot run follwoing (su password is ubuntu):                            ^|
@echo ^+                                                                                     ^|
@echo ^+          su                                                                         ^|
@echo ^+          adduser ubuntu sudo                                                        ^|
@echo ^+  and then reboot.                                                                   ^|
@echo ^+                                                                                     ^|
@echo ^+ and then:                                                                           ^|
@echo ^+          su                                                                         ^|
@echo ^+          cd ./Transfer                                                              ^|
@echo ^+          ./SU_Install_Common_and_GamingMachine.sh                                   ^|
@echo ^+                                                                                     ^|
@echo ^+=====================================================================================^+
@echo.
@echo.

goto end

:end
90
General (but related to Code::Blocks) / Re: something about M_PI
« Last post by stahta01 on September 07, 2021, 11:45:49 pm »
The file "gp_Dir2d.lxx" that I found in opencascade project was never meant to be treated as a source file as in being compiled.
Instead it should be treated as a header file and the compiling and linking turned off for the file.

So, the file extension of "lxx" should not be a problem. Still waiting for a build log!

Tim S.
 
Pages: 1 ... 4 5 6 7 8 [9] 10