Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
Development / Re: Non Windows Fortran plugin build query
« Last post by Miguel Gimenez on Today at 10:10:32 am »
prickscornful is not interested in the answer.

Profile spammer reported to moderator.
2
Help / Re: Terminal to launch consol programs is grayed and not working
« Last post by stahta01 on Today at 07:16:10 am »
The OP might want to look at the ToolPlus CB Plugin.

Tim S.
3
Development / Re: Non Windows Fortran plugin build query
« Last post by stahta01 on Today at 04:54:18 am »
I've built it on OS X from C::B using the "Unix 3.1" project file with help from the plugin's author via email.

The makefile provided with the repo is old, as it wasn't contributed by the Fortran plugin author,
and it hasn't been kept up to date with the revisions.
So do you know when it will have an update with the fixes?

What Operating System (OS) are you using?

Have you already build the core CB Project for that OS?

Tim S.
4
Development / Re: Non Windows Fortran plugin build query
« Last post by prickscornful on Today at 04:29:55 am »
I've built it on OS X from C::B using the "Unix 3.1" project file with help from the plugin's author via email.

The makefile provided with the repo is old, as it wasn't contributed by the Fortran plugin author,
and it hasn't been kept up to date with the revisions.
So do you know when it will have an update with the fixes?
5
Help / Re: Terminal to launch consol programs is grayed and not working
« Last post by Pecan on Yesterday at 06:39:13 am »
Thank you for your response. I would like to keep the console windows open all the time when I am working on a project.

Could you please let me know how can it be done.

Regards,

Hamid

I'm confused by this request. A console is either a stand-alone process that belongs to no project, or it is a console attached to a running project that takes input for the running project and accepts output from the running project.

How do you expect a console to be attached to a non-running project that you are working on?

If all you want is a console that is running on it's own behalf, in Windows, hit the windows key+r and type "cmd".

If you want a console attached to a process to accept input and produce output to the a console, write a program that reads (see reading from stdin) from a console and write output to the console (see writing to stdout).

Google "c++ stdin and stdout and stderr"

In C++, stdin, stdout, and stderr are standard input, output, and error streams, respectively. They allow you to interact with the console.
Here's a breakdown:

    stdin:
    Represents the standard input stream, typically connected to the keyboard. You can use it to read input from the user.
    stdout:
    Represents the standard output stream, typically connected to the console window. You can use it to write output to the console.
    stderr:
    Represents the standard error stream, typically connected to the console window. You can use it to write error messages to the console.

How to use them:

    cin: The cin object is used to read input from stdin.
    cout: The cout object is used to write output to stdout.
    cerr: The cerr object is used to write error messages to stderr.

Example:
C++

#include <iostream>

int main() {
    int number;

    // Read input from stdin
    std::cout << "Enter a number: ";
    std::cin >> number;

    // Write output to stdout
    std::cout << "You entered: " << number << std::endl;

    // Write error message to stderr
    std::cerr << "This is an error message!" << std::endl;

    return 0;
}

Important points:

    You need to include the <iostream> header to use these streams.
    cin, cout, and cerr are objects of classes istream, ostream, and ostream, respectively.
    You can use the >> operator with cin to read different data types.
    You can use the << operator with cout and cerr to write different data types.
    You can redirect these streams using the <, >, and 2> operators in the command line.
 
6
Development / Re: CB 24.12 & MAC
« Last post by Wkerry on December 03, 2024, 09:14:10 pm »
So GDB debugging works on the latest MAC OS?
Have you actually checked or assumed?

I am asking as there have been multiple reports on CB forum and on other forums that GDB has issues and it relates to a security change/changes Apple made a long time ago.
7
Development / Re: Add force switch to installation file
« Last post by olivier sc on December 03, 2024, 06:27:24 pm »
Or maybe add a real update process by a /update ?
8
Development / Re: Add force switch to installation file
« Last post by olivier sc on December 03, 2024, 06:26:30 pm »
Yes we have CalledProcessErrorOutput: Command '"codeblocks-20.03mingw-setup.exe" /S' returned non-zero exit status 2.
Just because old "codeblocks" is in place.

So add a /force option make sens to complet the update by overwriting.
9
Help / Re: Terminal to launch consol programs is grayed and not working
« Last post by hamid on December 03, 2024, 08:22:53 am »
Thank you for your response. I would like to keep the console windows open all the time when I am working on a project.

Could you please let me know how can it be done.

Regards,

Hamid
Pages: [1] 2 3 4 5 6 ... 10